Refactor Azure Storage API

[sebastienros]

Description

• Rename service‐level methods (AddBlobs, AddQueues, AddTables) to AddBlobService, AddQueueService, AddTableService (and their client‐builder equivalents).
• Introduce AddAzureQueueServiceClient, AddAzureQueue, and support for QueueClient registration alongside existing BlobServiceClient flows.
• Creates queues automatically (deployment and emulator).

I added the API diff to make it easier to see the new/obsolete methods. I don't think it will be necessary to remove these before merging (right?).

TBD:

• Generate playground app manifests
• Test all updated playground apps

Fixes #6875

Checklist

• Is this feature complete?
  • Yes. Ready to ship.
  • No. Follow-up changes expected.
• Are you including unit tests for the changes and scenario tests if relevant?
  • Yes
  • No
• Did you add public API?
  • Yes
    • If yes, did you have an API Review for it?
      • Yes
      • No
    • Did you add <remarks /> and <code /> elements on your triple slash comments?
      • Yes
      • No
  • No
• Does the change make any security assumptions or guarantees?
  • Yes
    • If yes, have you done a threat model and had a security review?
      • Yes
      • No
  • No
• Does the change require an update in our Aspire docs?
  • Yes
    • Link to aspire-docs issue (consider using one of the following templates):
      • [Breaking change]: Azure Storage APIs docs-aspire#3930
  • No

[Copilot]

Pull Request Overview

This PR refactors the Azure Storage API surface to unify naming, add first‐class support for queues and tables, and update all downstream usages (tests, samples, snapshots, docs) to the new methods.

• Rename service‐level methods (AddBlobs, AddQueues, AddTables) to AddBlobService, AddQueueService, AddTableService (and their client‐builder equivalents).
• Introduce AddAzureQueueServiceClient, AddAzureQueue, and support for QueueClient registration alongside existing BlobServiceClient flows.
• Update all test projects, snapshots, playground apps, and README docs to use the new APIs and adjust provisioning/infrastructure logic for queues and tables.

Comments suppressed due to low confidence (2)

tests/Aspire.Hosting.Azure.Tests/Snapshots/AzureStorageExtensionsTests.AddAzureStorageViaRunModeAllowSharedKeyAccessOverridesDefaultFalse.verified.bicep:26

• The snapshot removes the blobServices resource—ensure that the blob service resource is still generated when overriding shared key access defaults.

output blobEndpoint string = storage.properties.primaryEndpoints.blob

tests/Aspire.Hosting.Azure.Tests/AzureResourcePreparerTests.cs:55

• [nitpick] The variable blobs refers to a single BlobService resource—consider renaming to blobService to match the singular API method.

        var blobs = storage.AddBlobService("blobs");

[eerhardt]

Should this (and blob container) implement IResourceWithAzureFunctionsConfig?

[davidfowl]

I’d like this to go into 9.4

[eerhardt]

I think there are 2 things left that need to be addressed:

1. Functions support
2. What happens when AddBlobService is called more than once.

[eerhardt]

/backport to release/9.4

[github-actions]

Started backporting to release/9.4: https://github.com/dotnet/aspire/actions/runs/16179639157