[Spring Grove] Use workload identity to access Azure blob in SDK automation

[raych1]

Context
Currently, SDK automation uses a key to access Azure blob storage, and a SAS token is also used to construct an URL for accessing the blob. Per the Spring Grove requirement, we must replace the use of keys and SAS tokens for Azure blob access with managed identity.

Proposal
As SDK automation is integrated into the Azure DevOps pipeline, we can leverage the workload identity associated with a service connection to interact with Azure resources.

Specially, by using DefaultAzureCredential from azure/identity package, we can automatically fetch the workload identity in the Azure DevOps context. Additionally, it can fetch the token when debugging locally with Azure CLI login.

[raych1]

This issue has been fixed.