Unable to deploy Blazor wasm project to Aspire

### Is there an existing issue for this?

- [x] I have searched the existing issues

### Describe the bug

I have set up a new Aspire project to orchestrate my standalone Blazor Wasm and gRPC back-end solution. This was unsuccessful in deploy by Azd Up command, with the error message **BaseImageNotFoundException: The RuntimeIdentifier 'browser-wasm' is not supported by dotnet/runtime-deps:9.0-noble-chiseled-extra.**

I have tried many different things, but the last thing I tried was to set up a new Blazor Wasm app with everything default from project creation, add it to Apphost without doing anything else, but this also gives the same exception when deploying to a container in Azure.

### Expected Behavior

A container is created within the resource group connected to Aspire. It is deployed and available as front-end.

### Steps To Reproduce

1. Create an Aspire .NET 9 solution
2. Add a NET 9 Blazor wasm project
3. Add Blazor into apphost
var frontEnd2 = builder.AddProject("testfrontend")
.WithExternalHttpEndpoints();
4. Azd Init -> Azd Up

### Exceptions (if any)

BaseImageNotFoundException: The RuntimeIdentifier 'browser-wasm' is not supported by dotnet/runtime-deps:9.0-noble-chiseled-extra. The supported RuntimeIdentifiers are linux-x64,linux-arm,linux-arm64

### .NET Version info

.NET SDK:
Version: 9.0.100
Commit: 59db016f11
Workload version: 9.0.100-manifests.c6f19616
MSBuild version: 17.12.7+5b8665660

Runtime Environment:
OS Name: Windows
OS Version: 10.0.22621
OS Platform: Windows
RID: win-x64
Base Path: C:\Program Files\dotnet\sdk\9.0.100\

.NET workloads installed:
[aspire]
Installation Source: SDK 9.0.100, VS 17.13.35507.96, VS 17.12.35506.116
Manifest Version: 8.2.2/8.0.100
Manifest Path: C:\Program Files\dotnet\sdk-manifests\8.0.100\microsoft.net.sdk.aspire\8.2.2\WorkloadManifest.json
Install Type: Msi

[wasm-tools]
Installation Source: SDK 9.0.100
Manifest Version: 9.0.0/9.0.100
Manifest Path: C:\Program Files\dotnet\sdk-manifests\9.0.100\microsoft.net.workload.mono.toolchain.current\9.0.0\WorkloadManifest.json
Install Type: Msi

### Anything else?

Will probably change to Blazor Server, but this involves rather large refactor so would be good to get Blazor Wasm working for a while first.