[wasm] make it possible to enable emscripten assertions `-s ASSERTIONS=1`

[pavelsavara]

• migrate Blazor to new asset loading with maloc after onRuntimeInitialized
• -s ASSERTIONS=1 for debug build of runtime. It emits asserts to C and JS, it helps with debugging.

See also

• Blazor: Running Module.malloc too early? aspnetcore#13915
• [wasm] more emscripten asserts for debug build of runtime #62254

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

Issue Details

---

• migrate Blazor to new asset loading with maloc after onRuntimeInitialized
• -s ASSERTIONS=1 for debug build of runtime. It emits asserts to C and JS, it helps with debugging.

See also

• Blazor: Running Module.malloc too early? aspnetcore#13915
• [wasm] more emscripten asserts for debug build of runtime #62254

Author:	pavelsavara
Assignees:	pavelsavara
Labels:	arch-wasm, area-System.Runtime.InteropServices.JavaScript, blazor-wasm
Milestone:	8.0.0