Wasm tests on Windows are failing on gyp-next and this repo

[cclauss]

I don't have a good solution to fix the wasm test right now. I think we should disable it before we have a proper fix.

/cc author of the tests, @toyobayashi I'd appreciate it if you could help us fixing the test, thanks!

Originally posted by @legendecas in #3143 (comment)

• No available targets compatible with "wasm32"' gyp-next#287
• Python fixes for ruff v0.11.0 gyp-next#286 (comment)

@nodejs/wasi @nodejs/wasi

[toyobayashi]

The quickest solution is to install wasi-sdk in CI and then modify the path of clang.exe in the test code. If you agree to introduce additional dependencies, I can try to fix it. If you don't want to introduce additional dependencies, I think it's okay to skip the wasm test. I will open issue again if I encounter problems in the future. @legendecas @cclauss

[cclauss]

Great. Please try first on the gyp-next repo and then we can upgrade this repo from that one.

[legendecas]

The test is in this repo, not in gyp-next (gyp-next is failing because we run node-gyp tests in it).

[cclauss]

Confusing relationship between these two repos but OK.