[browser][MT] hybrid globalization

[pavelsavara]

plan A)

• make hybrid globalization not supported with MT
• tree-shake hybrid JS code via rollup WasmEnableThreads conditional compilation
• ideally move the code to sub-folder
• also conditonal ICALs in corebindings.c
• switch off HG tests with MT

plan B) - applied

• [x] reduce usage of mono_wasm_new_external_root, and stringToMonoStringRoot from hybrid
  • perhaps the string could be fixed in C# before making this call instead.
• [x] wrap_error_root,wrap_no_error_root` https://github.com/dotnet/runtime/issues/98365
• [x] because they interact with GC, which could lead to deadlock on UI thread.
• [ ] load rules json on all workers - working on it in https://github.com/dotnet/runtime/pull/102595

[ghost]

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

Issue Details

---

plan A) - make hybrid globalization not supported with MT - tree-shake hybrid JS code via rollup `WasmEnableThreads` conditional compilation - ideally move the code to sub-folder - also conditonal ICALs in `corebindings.c` plan B) - reduce usage of `mono_wasm_new_external_root`, `wrap_error_root`, `wrap_no_error_root` and `stringToMonoStringRoot` from hybrid - because they interact with GC, which could lead to deadlock on UI thread.

Author:	pavelsavara
Assignees:	ilonatommy
Labels:	`arch-wasm`, `area-VM-threading-mono`, `os-browser`
Milestone:	9.0.0