WASM globals are not managed by the netplay synchronization engine

[DenialAdams]

WASM globals are not managed by the netplay synchronization engine. As a result of this, two players on a cart using WASM globals can go out of sync.

We are at the mercy of compilers here, hoping that they choose to persistently store data in memory rather than in WASM global variables.

It is unknown (to me) how widespread the use of WASM globals is in compiler backends. There is at least one (Roland) that would run into this issue were it not for a WASM-4 specific check.

[DenialAdams]

One possible solution for this issue could be a cart pre-processing step that marks all global variables as exported, so that the WASM-4 runtime can observe them.