[wasm] pass ExitStatus when calling quit_

[pavelsavara]

For explanation Posix exit is implemented in emscripten as

1. On NodeJS it would also call process.exit and stop immediately.
2. Throwing javascript ExitStatus exception. That exception need to bubble thru all the call stack out into uncaughtException handler, which will recognize the class and swallow it. I think that going thru all the catch/finally statements it why it's designed this way. Also onV8 it's probably the only way how to stop, but I'm not sure now.

There is also noExitRuntime setting which could prevent that. We have it true on browser and I just set it to false on node and v8 in this PR.

Fixes #64727

[ghost]

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

Issue Details

---

Fixes #64727

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

[pavelsavara]

/azp run runtime-extra-platforms

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[pavelsavara]

/azp run runtime-extra-platforms

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[pavelsavara]

Log

[wasm test] [11:29:54] fail: {"name":"ExitStatus","message":"Program terminated with exit(42)","status":42}
[wasm test]                  
[wasm test] [11:29:54] info: Process node exited with 1
[wasm test]                  
[wasm test] [11:29:54] fail: Application has finished with exit code 1 but 42 was expected
[wasm test] [11:29:54] dbug: Saving diagnostics data to '/datadisks/disk1/work/A4E10928/w/B36509BA/e/diagnostics.json'
[wasm test] XHarness exit code: 71 (GENERAL_FAILURE)

[radekdoulik]

There's also:

[wasm test] [11:38:10] fail: Error
[wasm test]                  
[wasm test] [11:38:10] fail:     at Object.onAbort (test-main.js:157:25)
[wasm test]                  
[wasm test] [11:38:10] fail:     at abort (./dotnet.js:1973:24)
[wasm test]                  
[wasm test] [11:38:10] fail:     at Object.get (./dotnet.js:1116:7)
[wasm test]                  
[wasm test] [11:38:10] fail:     at Object.initializeImportsAndExports [as __initializeImportsAndExports] (./dotnet.js:3:83482)
[wasm test]                  
[wasm test] [11:38:10] fail:     at ./dotnet.js:7530:47
[wasm test]                  
[wasm test] [11:38:10] fail:     at test-main.js:123:12
[wasm test]                  
[wasm test] [11:38:10] fail: "Module.noExitRuntime has been replaced with plain noExitRuntime (the initial value can be provided on Module, but after startup the value is only looked for on a local variable of that name)"

in this log.

[radical]

In case it helps - I had found that set_exit_code was getting called twice for node.

1. set_exit_code(result), which would eventually call mono_wasm_exit-> exit, and that would throw an Error,
2. causing set_exit_code(1, error) to get called then

As a fix I changed test-main.js to explicitly call process.exit(result) on node.

[pavelsavara]

/azp run runtime-extra-platforms

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[pavelsavara]

/azp run runtime-extra-platforms

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[pavelsavara]

/azp run runtime-extra-platforms

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[pavelsavara]

/azp run runtime-extra-platforms

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).