wasm: add instantiateStreaming support

[danbev]

This commit adds instantiateStreaming support to allow for some
compatability with Web browser environments.

Refs: #21130

Whether or not this feature should be added as been discussed in above referenced issue. My motivation for wanting this is to allow a developer to write code that could be used in both web browser environments and in node.

Checklist

• make -j4 test (UNIX), or vcbuild test (Windows) passes
• tests and/or benchmarks are included
• commit message follows commit guidelines

[nodejs-github-bot]

@danbev sadly an error occured when I tried to trigger a build :(

[devsnek]

we should support passing a readable stream.

[devsnek]

@nodejs/v8 would it be possible to get v8::WasmStreaming before 7.0? i'd like to implement something like devsnek@ab9c03a

[TimothyGu]

Unfortunately, I don't think this PR quite changes the status quo with regards to the stated goal:

My motivation for wanting this is to allow a developer to write code that could be used in both web browser environments and in node.

One could already use other mechanisms to compile WASM modules on Node.js, and even if this PR were to be merged one would still have to use different code on Node.js vs. browsers to compile a module.

In fact, since this is incompatible with browser's instantiateStreaming implementation (which does not support Promise<TypedArray> as input), I don't believe this PR should land in Node.js.

[danbev]

In fact, since this is incompatible with browser's instantiateStreaming implementation (which does not support Promise as input), I don't believe this PR should land in Node.js.

Ah I see, I was mistakingly thinking that instantiateStreaming taking a promise this would work but realise my mistake here.

Sorry about the noice and thanks @TimothyGu and @devsnek for your feedback!