Provide more directive error message for errors from queryd-adjacent components

In a recent incident that was summarized here: https://github.com/influxdata/idpe/issues/7853,
we found unreliable behavior with query pods communicating to storage after storage pods are redeployed.

Specifically, we saw a lot of rpc errors:

We were spending time tracking down where did those error messages come from, and later we determined that it was actually from istio.

One of the take-aways from the investigation of this incident is that it will be very helpful if we could add additional information to those error messages stating which service we were trying to contact when we hit the error.

Start by locating the queryd-adjacent components that produce RPC errors when query pods contact storage pods, then trace how the contacted service is known at the error site. Reproduce or inspect the redeployment communication failure described in the incident and confirm that the resulting error identifies the service being contacted.

Written by the indexing model from the issue text.