"Just" an API vs requiring upstream features

I think #549 and WebAssembly/wasi-native-threads#48, present a qualitative change, however minor, from 'just an imported API' to where WASI would need some core features. I didn't think this should've prevented #549 from going forward, but I think it would be good to start a discussion on this.

In my view WASI is taking these dependencies on upstream standard, we can debate whether one is causing the other or they are independent:

• Component Model itself is a core proposal, at least far as APIs are concerned
• Certain features must be implemented in core wasm instead of APIs, as we have seen with threads

This is concerning, because so far there is not much traction in supporting component model or other core features mandated by the current WASI direction in browsers (treads draft hasn't been presented yet, for example). This would create divergence between WASI and 'stock' web environment, while more convergence would be preferrable in my opinion, as there are currently some challenges with running the same code both ways.

Originally posted by @penzn in https://github.com/WebAssembly/WASI/issues/549#issuecomment-1707400369

Start by reading #549 and wasi-native-threads#48, then review the discussion about the Component Model, core WebAssembly features, and browser support. Done would require a resolved position on whether WASI should depend on these upstream features and how to address divergence from the web environment.