Context

Address the review https://github.com/mongodb/mongo-go-driver/pull/2481#discussion_r3591161988 and https://github.com/mongodb/mongo-go-driver/pull/2481#discussion_r3633990993

Currently, an AzureCredentialProvider in x/mongo/driver/auth/creds/azurecreds.go uses the same AWS credential type and logic used by the AWSCredentialProvider. It also causes issues in Azure's credentials caching mechanism because Azure only uses SessionToken and AWS relies on AccessKeyID and SecretAccessKey.

Definition of done

• Separate the Azure credential type and logic from AWS credentials.
• Instead of using HasKey() to check AccessKeyID and SecretAccessKey, the Azure retrieval logic should rely on SessionToken.

Pitfalls

What should the implementer watch out for? What are the risks?