Chore(governance): Propose adding js-wasi-ext

[karthik2804]

This commit adds the js-wasi-ext to the spin project. This is a library compatible with WASI 0.2 that makes select Node.js APIs available in ComponentizeJS and StarlingMonkey. This library depends on the build tooling used in the Spin JS SDK. This enables having more library compatibility for npm packages with the Spin JS SDK.

TODO:

• The link in the doc is to be the URL once the repository is moved here.

[michelleN]

@itowlson brought up a good question in the spin project meeting around if it makes sense to host this project to the bytecode alliance. @karthik2804 do you have any thoughts around that?

[tschneidereit]

This PR is a result of conversations Karthik and I had, so I can provide some context. There are two key reasons for hosting this here instead of in the BA:

1. It relies pretty heavily on Spin's JS SDK. That could be overcome, but would be a meaningful amount of work. If that were the only issue, that'd totally be worth it. However:
2. js-wasi-ext is very much a short-term hack, not the approach we'll want to take in the long-term. We've had various conversations in the context of StarlingMonkey and ComponentizeJS about how to design a Node.js compatibility layer, and will definitely want build one, but we know that it'll look quite different from this. And in the meantime, this approach isn't easy to integrate into either project, so it'd be unclear how to even go about it.

[michelleN]

@tschneidereit that makes sense. Thanks for the context!