[browser][mt] Propagate unhandled JS errors in JSWebWorker to the top level Task

[lambdageek]

If user code uses setTimeout to queue work on the JSWebWorker and that code throws unhandled exceptions, we should not bring down the whole runtime in a disorganized manner.

Should we propagate unhandled JS errors the JSWebWorker top level Task ?

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

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

Issue Details

---

null

Author:	lambdageek
Assignees:	-
Labels:	arch-wasm, area-Threading-mono
Milestone:	-

[pavelsavara]

I guess we don't have any manifestation of this yet?

Anyway, I think that calling back from JS to C# will happen via JSExport and that propagates exceptions correctly.

Is there another concern ?