As a LokiStack administrator I want to off-load Azure WIF configuration to the CloudCredentialOperator when running on a cluster that supports this operator so that I do not need to manually manage WIF credentials configuration on Azure and in turn a custom LokiStack Azure object storage secret.

Acceptance Criteria

• The Loki Operator offloads all Azure WIF credential generation work to the CloudCredentialOperator on OpenShift platforms with this operator available.
• The LokiStack administrator is required to provide only a very minimum S3 object storage config secret, i.e. environment, container, endpoint_suffix
• The Loki Operator needs to declare in the ClusterServiceVersion provided for OpenShift the following annotation: features.operators.openshift.io/token-auth-azure

Developer Notes.

1. Consider reading and understanding the recommended approach from this documentation: https://docs.google.com/document/d/1iFNpyycby_rOY1wUew-yl3uPWlE00krTgr9XHDZOTNo/edit
2. The Loki Operator needs to check (periodically) if the present APIServer supports the custom resource CredentialsRequest from cloudcredential.openshift.io/v1.
3. For tenant modes openshift-logging and openshift-network the operator will create a CredentialsRequest:
   1. In the CloudCredentialOperator namespace.
   2. Provide a list of required Azure rights as listed here https://grafana.com/docs/loki/v2.9.x/storage/#azure-deployment-azure-blob-storage-single-store
   3. Reference a secret in the openshift-logging/netobserv namespace for the CloudCredentialOperator.
4. Upon the CloudCredentialOperator providind the secret (that includes the client_id and tenant_id, federated_token_file) the Loki Operator resumes operations as in LOG-4546 to connect configure Loki's azure config for WIF.