Version of components:

observability-operator.v0.3.0-dev-0.1.1
quay.io/rhn_support_ikanse/observability-operator-bundle:0.3.0-dev-0.1.1
OCP version 4.15.19

Description of the problem:
When multitenancy is enabled for TempoStack instance, distributed-tracing-console plugin is not able to connect to TempoStack and we see the following error in the plugin pod.

10.130.0.100 - - [21/Jun/2024:10:10:05 +0000] "GET /plugin-manifest.json HTTP/1.1" 200 733
2024/06/21 10:10:17 httputil: ReverseProxy read error during body copy: read tcp 10.129.2.26:45704->172.30.183.246:3200: read: connection reset by peer
10.130.0.100 - - [21/Jun/2024:10:10:19 +0000] "GET /plugin-manifest.json HTTP/1.1" 200 733
10.130.0.100 - - [21/Jun/2024:10:10:34 +0000] "GET /plugin-manifest.json HTTP/1.1" 200 733
10.130.0.100 - - [21/Jun/2024:10:10:50 +0000] "GET /plugin-manifest.json HTTP/1.1" 200 733 

Steps to reproduce the issue:
*Install Observability Operator built off the upstream main branch.
*Create the distributed-tracing-console-plugin resource.
*Create a TempoStack with multitenancy enabled by following the steps from this chainsaw-test.yaml file. We just need to follow the steps and create the resources one-by-one by running oc apply. Resource files path 
*Once the TempoStack is created try searching for Traces by selecting the stack from OCP web console > Observe > Traces.