[wasm] Host should separate arguments for engine, mono and application

[pavelsavara]

Possible designs
A) use multiple -- to separate it
node --enable-source-maps main.js -- hello.dll --setenv=XXX=1 -- -fromCity=Prague to Ilona

--enable-source-maps is nodeJS engine flag
--setenv=XXX=1 is mono engine flag
-fromCity=Prague is application argument
to is application arg
Ilona is application arg

dotnet run --engine=node -- --enable-source-maps main.js -- hello.dll --setenv=XXX=1 -- -fromCity=Prague to Ilona

this assumes that main.js which is user will call .withRuntimeOptionsFromArguments() to consume it.

B) use well know pass-thru arguments

wasmtime run --env MONO_OPTIONS="values" dotnet.wasm

dotnet run --engine=wasmtime --engine-arg='--env MONO_OPTIONS="values"' dotnet.wasm

escaping becomes nasty.

Also, from #85674 (comment)
Perhaps there should be pass-thru argument like --host:xxx=yyyand--runtime:aaa=bbbbefore application -- ? As an alternative to multiple -- .

More details discussed here #70892

[ghost]

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

Issue Details

---

Possible designs
A) use multiple -- to separate it
node --enable-source-maps main.js -- hello.dll --setenv=XXX=1 -- -fromCity=Prague to Ilona

--enable-source-maps is nodeJS engine flag
--setenv=XXX=1 is mono engine flag
-fromCity=Prague is application argument
to is application arg
Ilona is application arg

dotnet run --engine=node -- --enable-source-maps main.js -- hello.dll --setenv=XXX=1 -- -fromCity=Prague to Ilona

this assumes that main.js which is user will call .withRuntimeOptionsFromArguments() to consume it.

B) use well know pass-thru arguments

wasmtime run --env MONO_OPTIONS="values" dotnet.wasm

dotnet run --engine=wasmtime --engine-arg='--env MONO_OPTIONS="values"' dotnet.wasm

escaping becomes nasty.

More details discussed here #70892

Author:	pavelsavara
Assignees:	radical
Labels:	arch-wasm, os-browser
Milestone:	8.0.0

[radical]

Moving this to 9.0, so we can get an agreement on how this should be done, as it should be consistent with how dotnet run handles these kinda cases.

[pavelsavara]

cc @richlander