[browser][MT] Schedule mono_wasm_resolve_or_reject_promise continuation to run asynchronously

[pavelsavara]

Theory of this fix:

• passing Task to JS as parameter of async JSImport with virtual JSHandle -2 allocated with AllocJSVHandle()
• mono_wasm_resolve_or_reject_promise is executed before the mono_wasm_invoke_jsimport
• both are async messages via mono_threads_wasm_async_run_in_target_thread and they could be deliverd in this order in case that the task is already resolved
• so that task.ContinueWith(Complete, ... is executed synchronously from inside of ToJS(Task? value)

contributes to #98406

[ghost]

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

Issue Details

---

Theory of this fix:

• passing Task to JS as parameter of async JSImport with virtual JSHandle -2 allocated with AllocJSVHandle()
• mono_wasm_resolve_or_reject_promise is executed before the mono_wasm_invoke_jsimport
• both are async messages via mono_threads_wasm_async_run_in_target_thread and they could be deliverd in this order in case that the task is already resolved
• so that task.ContinueWith(Complete, ... is executed synchronously from inside of ToJS(Task? value)

contributes to #98406

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

[lewing]

I like the theory

[pavelsavara]

I'm afraid it didn't help 😦
https://helixre107v0xdcypoyl9e7f.blob.core.windows.net/dotnet-runtime-refs-pull-99296-merge-aa17b7698c46456799/WasmTestOnBrowser-System.Runtime.InteropServices.JavaScript.BackgroundExec.Tests/1/console.f27a5995.log?helixlogtype=result