[MT][browser] ` Wasm.Browser.Config.Sample`, `Wasm.Browser.Config.Sample` fail

[ilonatommy]

Failing after enabling all MT library tests (#91536).

Wasm.Browser.Config.Sample:

Single asset for js-module-threads not found Error: Assert failed: Single asset for js-module-threads not found
    at Je (globals.ts:141:19)
    at assets.ts:126:5
WASM EXIT 1

Minimal config needs 2 versions: for MT and for ST, MT adding:

    {
        name: "dotnet.native.worker.js",
        behavior: "js-module-threads"
    },

Then, we're getting setRuntimeGlobals is not a function, probably because config is not loaded properly - "demo imports / promises" are embedded in the minimal config and are not getting resolved. We would need a callback to main.js on the worker to fulfill them.

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Failing after enabling all MT library tests (#91536).

fail: [out of order message from the browser]: http://127.0.0.1:34379/_framework/dotnet.js 2:18480 Uncaught Error: Assert failed: SharedArrayBuffer is not enabled on…ers. See also https://aka.ms/dotnet-wasm-features
info: Waiting to flush log messages with a timeout of 120 secs ..
fail: Flushing log messages failed with: System.OperationCanceledException: The operation was canceled.
         at System.Threading.Channels.AsyncOperation`1.GetResult(Int16 token)
         at System.Threading.Channels.ChannelReader`1.ReadAllAsync(CancellationToken cancellationToken)+MoveNext()
         at System.Threading.Channels.ChannelReader`1.ReadAllAsync(CancellationToken cancellationToken)+System.Threading.Tasks.Sources.IValueTaskSource<System.Boolean>.GetResult()
         at Microsoft.DotNet.XHarness.CLI.Commands.Wasm.WasmTestMessagesProcessor.RunAsync(CancellationToken token) in /_/src/Microsoft.DotNet.XHarness.CLI/Commands/WASM/WasmTestMessagesProcessor.cs:line 68
         at Microsoft.DotNet.XHarness.CLI.Commands.Wasm.WasmTestMessagesProcessor.RunAsync(CancellationToken token) in /_/src/Microsoft.DotNet.XHarness.CLI/Commands/WASM/WasmTestMessagesProcessor.cs:line 68
         at Microsoft.DotNet.XHarness.CLI.Commands.Wasm.WasmTestMessagesProcessor.CompleteAndFlushAsync(Nullable`1 timeout) in /_/src/Microsoft.DotNet.XHarness.CLI/Commands/WASM/WasmTestMessagesProcessor.cs:line 140. Ignoring.
fail: Tests timed out. Killing driver service pid 80
fail: Application has finished with exit code TIMED_OUT but 0 was expected

Author:	ilonatommy
Assignees:	-
Labels:	arch-wasm, disabled-test, area-Build-mono, area-VM-threading-mono
Milestone:	-

[pavelsavara]

If you start samples with /p:WasmEnableThreads=true they should work.
The question is if we are able sniff what kind of runtime we already have locally and use the same flavor for the samples automatically.