Proposed title of this feature request

Support following short lived object storage token authentication:

• GCP Workload Identity Federation
• Azure identity workload federation 
• AWS STS via cloudcredential operator https://www.redhat.com/en/blog/running-pods-in-openshift-with-aws-iam-roles-for-service-accounts-aka-irsa 

Feature parity with Loki: https://loki-operator.dev/docs/short_lived_tokens_authentication.md/#gcp-workload-identity-federation 

What is the nature and description of the request?

As it happened in OBSDA-794 for AWS S3, Tempo supports AWS S3 access via access key and secret key. To access S3, we typically create a secret in OpenShift containing these keys. However, the customer's SIEM team does not permit storing secrets locally on the cluster.

While this is alreaady solved for S3, we need to fix this of other cloud providers: GCP and Azure.

Check:https://github.com/grafana/tempo-operator/issues/956