Proposal: WASI WIT artifacts should include `unstable` features

[ricochet]

We have been releasing WASI artifacts with: wkg wit build --wit-dir .. By default, this does not include unstable features.

Proposal is to change the artifact that we release as part of our train model to include unstable features. The annotations for unstable will be retained so downstream parsers may select for only stable features or opt-in to the set of unstable features.

For additional context: bytecodealliance/wasm-pkg-tools#144

Past presentations walking through the process:

• https://github.com/WebAssembly/meetings/blob/main/wasi/2024/presentations/2024-05-30-yosh-wuyts-leveraging-since-unstable-gates-in-wasi.pdf
• https://github.com/WebAssembly/meetings/blob/main/wasi/2024/presentations/2024-06-13-yosh-wuyts-progressing-proposal-changes-through-the-phase-process.pdf

[lann]

This appears to be done with 0.2.4?

[ricochet]

We used the latest wkg release that included your fix bytecodealliance/wasm-pkg-tools#147

Verifying that the artifacts all included their unstable features definitions:

wkg oci pull "ghcr.io/webassembly/wasi/clocks:0.2.4"
Successfully wrote ghcr.io/webassembly/wasi/clocks:0.2.4 to webassembly_wasi_clocks.wasm
wasm-tools component wit webassembly_wasi_clocks.wasm | grep unstable
@unstable(feature = clocks-timezone)
  @unstable(feature = clocks-timezone)
  @unstable(feature = clocks-timezone)
  @unstable(feature = clocks-timezone)
  @unstable(feature = clocks-timezone)
  @unstable(feature = clocks-timezone)

wkg oci pull "ghcr.io/webassembly/wasi/cli:0.2.4"
wasm-tools component wit webassembly_wasi_cli.wasm | grep unstable
  @unstable(feature = cli-exit-with-code)
  @unstable(feature = clocks-timezone)
  @unstable(feature = clocks-timezone)

wkg oci pull "ghcr.io/webassembly/wasi/sockets:0.2.4"
wasm-tools component wit webassembly_wasi_sockets.wasm | grep unstable
  @unstable(feature = network-error-code)
  @unstable(feature = network-error-code)

wkg oci pull "ghcr.io/webassembly/wasi/http:0.2.4"
Successfully wrote ghcr.io/webassembly/wasi/http:0.2.4 to webassembly_wasi_http.wasm
wasm-tools component wit webassembly_wasi_http.wasm | grep unstable
    @unstable(feature = informational-outbound-responses)

Related to this change, we future-proofed wasi repos to always check for all-features vs individual features, e.g. https://github.com/WebAssembly/wasi-sockets/pull/117/files.