Running WASM on All Solution Doesn't work in VS

### Describe the bug

Related to #306

If I generate the solution and build it in VS, and then run WASM from the commandline:

```
dotnet run --project tooling\ProjectHeads\AllComponents\Wasm\CommunityToolkit.App.Wasm.csproj
```

Everything works as expected.

But if I run from VS, it doesn't work, the call to `WasmAppHost` fails as it's looking at the wrong path:

```
WasmAppHost --use-staticwebassets --runtime-config I:\code\Labs-Windows\tooling\ProjectHeads\AllComponents\Wasm\bin\Debug\net9.0\CommunityToolkit.App.Wasm.runtimeconfig.json
```
(Notice the `browser-wasm` subfolder is missing)

Correct command:
```
WasmAppHost --use-staticwebassets --runtime-config I:\code\Labs-Windows\tooling\ProjectHeads\AllComponents\Wasm\bin\Debug\net9.0\browser-wasm\CommunityToolkit.App.Wasm.runtimeconfig.json
```

### Steps to reproduce

```text
1. Clone repo
2. GenerateAllSolution.bat
3. Run WASM head in VS

Fails to run
```

### Expected behavior

Run WASM head

### Screenshots

_No response_

### Code Platform

- [ ] UWP
- [ ] WinAppSDK / WinUI 3
- [x] Web Assembly (WASM)
- [ ] Android
- [ ] iOS
- [ ] MacOS
- [ ] Linux / GTK

### Windows Build Number

- [ ] Windows 10 1809 (Build 17763)
- [ ] Windows 10 1903 (Build 18362)
- [ ] Windows 10 1909 (Build 18363)
- [ ] Windows 10 2004 (Build 19041)
- [ ] Windows 10 20H2 (Build 19042)
- [ ] Windows 10 21H1 (Build 19043)
- [ ] Windows 11 21H2 (Build 22000)
- [ ] Other (specify)

### Other Windows Build number

_No response_

### App minimum and target SDK version

- [ ] Windows 10, version 1809 (Build 17763)
- [ ] Windows 10, version 1903 (Build 18362)
- [ ] Windows 10, version 1909 (Build 18363)
- [ ] Windows 10, version 2004 (Build 19041)
- [ ] Other (specify)

### Other SDK version

_No response_

### Visual Studio Version

2022

### Visual Studio Build Number

_No response_

### Device form factor

_No response_

### Additional context

Tried in VS 2026 as well, had a few more issues trying to build there.

### Help us help you

No, I'm unable to contribute a solution.