Change the order of credentials in the DefaultAzureCredential

[antkmsft]

@scottaddie: "Wow the order of credentials was determined in the C++ DefaultAzureCredential. We typically put the dev tool credentials at the very end of the chain. We see Managed Identity as more important."
@antkmsft: "The order is the one I presented to the C++ team initially, but you are right, we should try to change it. Initially, I think, ManagedIdentityCredential was at the end because unlike other languages, our ManagedIdentityCredential does not probe the IP address yet, and just tries to get the token. But still, that should not be the factor that prevents it from being in the middle of the chain. The good thing is that everywhere in documentation we say that although we are documenting the order of credentials, we may change their order in the future, and that would not be considered a breaking change. So let me to open an issue to change the order, and update the docs and the SVG."

[ahsonkhan]

Here are the order that other languages are following:

1. Environment
2. WorkloadIdentity
3. ManagedIdentity
4. AzureCli/Dev-specific credentials like IntelliJ/etc.

https://github.com/Azure/azure-sdk-for-go/blob/e7968b534c61da1e38a683e21ac690deb14833c7/sdk/azidentity/default_azure_credential.go#L46C1-L51

https://github.com/Azure/azure-sdk-for-java/blob/26bd513d93b5301797d7127cf4f6f55ae81c47c6/sdk/identity/azure-identity/src/main/java/com/azure/identity/DefaultAzureCredential.java#L19-L35

https://github.com/Azure/azure-sdk-for-net/blob/a932f53e2fc200cee443614a0bf991b02b518055/sdk/identity/Azure.Identity/src/Credentials/DefaultAzureCredential.cs#L17-L28

[ahsonkhan]

Re-opening #5156 until we fix the responsiveness of ManagedIdentityCredential on failure.
#4952

[github-actions]

Hi @antkmsft, we deeply appreciate your input into this project. Regrettably, this issue has remained unresolved for over 2 years and inactive for 30 days, leading us to the decision to close it. We've implemented this policy to maintain the relevance of our issue queue and facilitate easier navigation for new contributors. If you still believe this topic requires attention, please feel free to create a new issue, referencing this one. Thank you for your understanding and ongoing support.