Blazor WASM: SDK 9.0.312 regression – app fails at startup (mono_wasm_load_runtime) vs 9.0.311

### Is there an existing issue for this?

- [x] I have searched the existing issues

### Describe the bug

Blazor WebAssembly app works correctly when built with .NET SDK 9.0.311 but fails at runtime startup when built with 9.0.312.

This appears to be a regression introduced between these SDK versions.

Environment
OS: Debian 12 (Linux)
SDK working: 9.0.311
SDK broken: 9.0.312
Workload: wasm-tools
Hosting: static (python http.server)

Turn on AOT:

`true`

Publish the Build:
dotnet publish -c Release

Launch a test server:

cd bin/Release/net9.0/publish/wwwroot
python3 -m http.server 8080

then load in Chrome browser, notice the failure:

MONO_WASM: mono_wasm_load_runtime () failed
Uncaught (in promise) ExitStatus
Failed to start platform

Downgrading only the SDK (no code changes), then rebuilding, immediately resolves the issue.

I have not yet reduced this to a minimal repro; I can attempt to provide one after my upcoming release if needed. For now, I am pinned to SDK 9.0.311 as a workaround.

### Expected Behavior

_No response_

### Steps To Reproduce

_No response_

### Exceptions (if any)

_No response_

### .NET Version

9.0.312

### Anything else?

_No response_