Allow Azure Auth order to be specified via azureAuthMethods component metadata

[berndverst]

Description

Fixes #3183

Implements support for specifying the order of Azure Authentication methods to try. This allows an admin to also exclude authentication methods, or to complete disallow Azure authentication.

This is accomplished via a new global component metadata field for all Azure components azureAuthMethods. This field accepts a string of comma-separated values from the following list: ServicePrincipal, Certificate, WorkloadIdentity, ManagedIdentity, CLI, None

If the list contains None as one of the options, all Azure Auth will be disabled regardless of other options listed.

If azureAuthMethods is empty, or omitted (default behavior), then the current default behavior is maintained:

// 1. Client credentials
// 2. Client certificate
// 3. Workload identity
// 4. MSI (we use a timeout of 1 second when no compatible managed identity implementation is available)
// 5. Azure CLI

Issue reference

We strive to have all PR being opened based on an issue, where the problem or feature have been discussed prior to implementation.

Please reference the issue this PR will close: #3183

Checklist

Please make sure you've completed the relevant tasks for this PR, out of the following list:

• Code compiles correctly
• Created/updated tests
• Extended the documentation / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]

[berndverst]

/ok-to-test

[dapr-bot]

Components certification test

🔗 Link to Action run

Commit ref: 67940b3

❌ Some certification tests failed

These tests failed:

• bindings.azure.servicebusqueues
• secretstores.hashicorp.vault

[dapr-bot]

Complete Build Matrix

The build status is currently not updated here. Please visit the action run below directly.

🔗 Link to Action run

Commit ref: 67940b3

[dapr-bot]

Components conformance test

🔗 Link to Action run

Commit ref: 67940b3

✅ All conformance tests passed

All tests have reported a successful status