runtime: async preemption (or alternative) for wasm

[prattmic]

This is split from #65178, as the specific scheduler bug was fixed.

Due to its single-threaded nature, js/wasm have no sysmon thread, and thus no asynchronous preemption. Thus the pitfalls of Go prior to asynchronous preemption apply: tight loops that fail to yield may delay scheduling indefinitely.

This is a tracking issue for problems due to the lack of asynchronous preemption. As noted in #36365, due to the lack of threading, asynchronous preemption isn't possible today, but perhaps could be with wasm threads? Or we could have an alternative scheme for js/wasm (such as adding preemption points to loops).

(Plan9 is also missing async preemption, but that simply needs an implementation)

[Zxilly]

I have two ideas, one idea is to reimplement sysmon in js and rely on asynchronous scheduling on the js side to run it, but this would require runtime to expose a lot of internal interfaces in wasm, and it would also take extra effort to keep the js implementation consistent with the go implementation.
Another idea could be to start pushing for wasm thread support, but given that this is a relatively new feature, we still need to make sure it functions properly without wasm thread support. Also, additional COOP and COEP headers need to be configured to enable SharedArrayBuffer, which makes deployment difficult.

[cherrymui]

I agree that using Wasm threads is probably the way to go. I don't think this is urgent, so we can probably wait until wasm threads are generally available. If we need anything urgent in the mean time, we could insert manual preemption point in specific code paths.

(Plan9 is also missing async preemption, but that simply needs an implementation)

https://go.dev/cl/228893 (and the stack) was an attempt. The main difficulty is the lack of the equivalent of SA_RESTART, so I have to restart interrupted syscalls manually. Due the the low availability and stability of the builders, I was not able to test the changes successfully.

[cherrymui]

This also applies to wasip1/wasm (not just js).

[gopherbot]

Change https://go.dev/cl/640195 mentions this issue: os: skip force the goroutine to be scheduled on WASM