[wasm] Design application startup, template, configuration

[pavelsavara]

TODO

• Adopt blazor.boot.json like format, instead of mono-config.json
• Separate assets/manifest from application config from current run arguments
• Unify the templates and it's runArgs.json
• PATH-like DLL resolution for nodeJS, (and WASI?)
• runtimeconfig.json/.bin and launchsettings
• remove features like proxyConsoleMethod from template, or integrate them with runtime
• Incremental updates
• Try to load assemblies to VFS (instead of WASM memory) and let runtime load them from there
• [wasm][nodejs] implement synchronous DLL loading #79981 - on NodeJS/V8 let runtime load assemblies on the fly from local filesystem without extra boot config
• Experiment with serializing initial wasm memory instead of loading dlls
• Experiment with inlined mono-config (faster startup, in-place URLs of all assets)
• [browser] Split dotnet.js and introduce loader + emscripten modules #85045

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

Issue Details

---

TODO

• Adopt blazor.boot.json like format, instead of mono-config.json
• Separate assets/manifest from application config from current run arguments
• Unify the templates and it's runArgs.json
• PATH-like DLL resolution for nodeJS, (and WASI?)
• runtimeconfig.json/.bin and launchsettings
• remove features like proxyConsoleMethod from template, or integrate them with runtime

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

[pavelsavara]

If we package dotnet.js as npm module, we should probably include the runtime DLLs in the package.
I experimentally did it at npm package and demo

Current problem is that it uses mono-config.json with "assembly_root": "managed", which is relatetive to dotnet.js.
That is trying to load C:\Dev\runtime-npm\demo\node_modules\@pavelsavara\dotnet-runtime/managed/Microsoft.CSharp.dll

But I don't have managed subfolder there. I'm not sure I like the managed subfolder.
Anyway, the location doesn't contain Demo.dll and mono-config.json probably can't handle multiple folders either.

[radical]

I believe we have completed some of the items, and others will have to be in 8.0 .