Draft: Add SSO support for Tempo when on `tempo.*` hostname

General MR

Summary

When Tempo is on tempo.<domain> the Authservice match ends up as tempo based on the prefix. This results in internal cluster services (named tempo-... by default) also matching this chain and being blocked by Authservice.

To workaround this we can rename the pods/svcs anytime the VS prefix is Tempo. This MR handles the two cases where this would be true:

• Customer overrides the VS host name directly
• Jaeger and Tempo are both enabled, BB changes the hostname to tempo under the hood