tenant-setting service is not reachable if not using ingress for routing

#### Describe the bug
We did add https://github.com/grafana/explore-profiles to our Grafana instance and also brought up `tenant-setting` and `adhoc-profiles` by using the latest version of the pyroscope helm chart which did re-add them as mentioned in https://github.com/grafana/pyroscope/issues/3463#issuecomment-2268419795.

We're running pyroscope in microservice mode without the ingress resources as we're not exposing it externally, this means alloy and Grafana do connect to the services directly.
In the case of Grafana we do connect to the query-frontend on `http://grafana-pyroscope-query-frontend.pyroscope.svc.cluster.local:4040`.
We're however ending up receiving a 404 on the settings page of "Explore Profiles" which also make some features unavailable.

Looking at other Grafana components, they mostly ship with a gateway which is responsible for those routing aspects. There is however no gateway component provided for Pyroscope. Is my assumption correct, that using the https://github.com/grafana/explore-profiles plugin currently does not work within the setup mentioned above?

#### Environment

- Grafana 11.1.3
- explore-profiles 0.1.5
- Pyroscope 1.7.1

Start with the latest Pyroscope Helm chart and reproduce the microservice-mode setup without ingress, using the direct query-frontend service address described in the issue. Trace how requests for tenant-setting and adhoc-profiles are routed; done means Explore Profiles settings no longer return 404 and the affected features work without ingress resources.

Written by the indexing model from the issue text.