Make Uno001 an error on Uno heads

### Describe the bug

It's easy to miss `Uno001` errors about something not being supported on Uno Platform during development (as the warning window is usually a mess and easy to ignore).

We'd like to have a nice way to better highlight these issues before they get hit in the CI when warnings turn to errors.

However, we don't want to disrupt early prototyping by having these be blockers from running code.

In this regard, we feel a good solution is to have a middle-ground.

If you run the UWP or Windows App SDK heads, nothing should change.

If you run a WASM head, then Uno001's will be flagged as errors instead of warnings, thus you'll need to fix them to continue testing on Uno.

This provides an easy path to test and prototype and then a way to check and bubble up these issues locally easily before submitting to the CI.

### Steps to reproduce

```text
N/A
```

### Expected behavior

Able to detect Uno001 issues more easily.

### 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

_No response_

### Visual Studio Build Number

_No response_

### Device form factor

_No response_

### Additional context

We won't worry about this for other all-up heads for Uno until we focus on enabling those more easily later with work related to #17.

### Help us help you

Yes, but only if others can assist.

No implementation files or tests are named in the issue, so start by locating the build or analyzer configuration that distinguishes WASM heads from UWP and Windows App SDK heads. Verify that Uno001 is treated as an error only for WASM while the other heads retain their current warning behavior.

Vom Indexierungsmodell aus dem Issue-Text verfasst.