Update image-registry to consume Azure workload identity tokens

This effort is dependent on the completion of work for CCO-187, and effort in dependent modules is planned to be worked on by the CCO team unless individual repo owners can help. Operators owners/teams will be expected to review merge requests and complete appropriate QE effort for an openshift release.

• azure-sdk-for-go module dependency updated to support workload identity federation.
  • Support for workload identity federation is not yet complete for azure-sdk-for-go. Support is being tracked in the following issues,
    • Azure/azure-sdk-for-go#15615
    • Azure/azure-sdk-for-go#17417
• Mount the OIDC token in the operator pod. This needs to go in the deployment. See example from addition to the cluster-image-registry-operator here

ACCEPTANCE CRITERIA

• image-registry uses latest openshift/docker-distribution
• CIRO can detect when the creds it gets from CCO are for federated workload identity (the credentials secret will contain a "azure_federated_token_file")
• when using federated workload identity, CIRO adds the "AZURE_FEDERATED_TOKEN_FILE" env var to the image-registry deployment
• when using federated workload identity, CIRO does not add the "REGISTRY_STORAGE_AZURE_ACCOUNTKEY" env var to the image-registry deployment
• the image-registry operates normally when using federated workload identity