`dotnet watch` with `aot` leads to unexpected behavior

1. Setup blazor wasm project with aot
2. Ensure the `wasm-tools` workload is **NOT** installed
3. Do `dotnet watch`

Expected: Error, missing workload, `dotnet watch` exits
Actual: Error, but `dotnet watch` is still running (and restarting) on file change, but dev server doesn't appear.

```
dotnet watch
watch : Hot reload enabled. For a list of supported edits, see https://aka.ms/dotnet/hot-reload. Press "Ctrl + R" to restart.
watch : Building...
Determining projects to restore...
/usr/local/share/dotnet/sdk/6.0.100-rc.2.21463.12/Sdks/Microsoft.NET.Sdk/targets/Microsoft.NET.Sdk.ImportWorkloads.targets(38,5): error NETSDK1147: To build this project, the following workloads must be installed: wasm-tools [/Users/tanay/dev/NoteTakingSample/NoteTakingSample.csproj]
/usr/local/share/dotnet/sdk/6.0.100-rc.2.21463.12/Sdks/Microsoft.NET.Sdk/targets/Microsoft.NET.Sdk.ImportWorkloads.targets(38,5): error NETSDK1147: To install these workloads, run the following command: dotnet workload install wasm-tools [/Users/tanay/dev/NoteTakingSample/NoteTakingSample.csproj]
watch : Waiting for a file to change before restarting dotnet...
```