Refactor connection string secret output assignment in Azure CosmosDB and Redis extensions

Author: davidfowl

src/Aspire.Hosting.Azure.CosmosDB/AzureCosmosDBExtensions.cs

@@ -346,8 +346,9 @@ public static IResourceBuilder<AzureCosmosDBResource> WithAccessKeyAuthenticatio
     {
         ArgumentNullException.ThrowIfNull(builder);
 
-        builder.Resource.ConnectionStringSecretOutput = keyVaultBuilder.Resource.GetSecretReference(
-            $"{builder.Resource.Name}--connectionString");
+        var azureResource = builder.Resource;
+        azureResource.ConnectionStringSecretOutput = keyVaultBuilder.Resource.GetSecretReference(
+            $"{azureResource.Name}--connectionString");
 
         builder.WithParameter(AzureBicepResource.KnownParameters.KeyVaultName, keyVaultBuilder.Resource.NameOutputReference);
 

src/Aspire.Hosting.Azure.Redis/AzureRedisExtensions.cs

@@ -209,7 +209,8 @@ public static IResourceBuilder<AzureRedisCacheResource> WithAccessKeyAuthenticat
         ArgumentNullException.ThrowIfNull(builder);
         ArgumentNullException.ThrowIfNull(keyVaultBuilder);
 
-        builder.Resource.ConnectionStringSecretOutput = keyVaultBuilder.Resource.GetSecretReference($"{builder.Resource.Name}--connectionString");
+        var azureResource = builder.Resource;
+        azureResource.ConnectionStringSecretOutput = keyVaultBuilder.Resource.GetSecretReference($"{azureResource.Name}--connectionString");
         builder.WithParameter(AzureBicepResource.KnownParameters.KeyVaultName, keyVaultBuilder.Resource.NameOutputReference);
 
         // remove role assignment annotations when using access key authentication so an empty roles bicep module isn't generated