ACA Container volumes use shared access keys

[eerhardt]

When using container volumes in an ACA app, we are generating an Azure Storage account for storing those volumes.

However, the way the access from ACA to this storage account happens is via access keys:

aspire/src/Aspire.Hosting.Azure.AppContainers/AzureContainerAppExtensions.cs

Lines 202 to 215 in 8fd92af

	var keysExpr = storageVolume.GetKeys()[0].Compile();
	var keyValue = new MemberExpression(keysExpr, "value");
	var containerAppStorage = new ContainerAppManagedEnvironmentStorage(managedStorageName)
	{
	Parent = containerAppEnvironment,
	ManagedEnvironmentStorageAzureFile = new()
	{
	ShareName = share.Name,
	AccountName = storageVolume.Name,
	AccountKey = keyValue,
	AccessMode = ContainerAppAccessMode.ReadWrite
	}
	};

This means that an Azure Storage account is created that allows shared key access, which may trigger security rules in environments that don't want to allow Azure Storage accounts with access keys.

We should be using managed identities here instead, to allow communication between the ACA container and the Storage account.

[davidfowl]

We need this to exposed this on the azure resource Azure/azure-sdk-for-net#50359