WASIP3 update to latest rc (#12781)

chore: bump to wasi 0.3.0-rc-2026-02-09 (#12557)

feat(p3)!: vendor 0.3.0-rc-2026-01-06 (#12250)

* feat(p3)!: vendor 0.3.0-rc-2026-01-06

Update wasmtime's WASI implementation from version
0.3.0-rc-2025-09-16 to 0.3.0-rc-2026-01-06, using wkg for W

feat(p3)!: vendor 0.3.0-rc-2026-01-06 (#12250)

* feat(p3)!: vendor 0.3.0-rc-2026-01-06

Update wasmtime's WASI implementation from version
0.3.0-rc-2025-09-16 to 0.3.0-rc-2026-01-06, using wkg for WIT vendoring.

This involves API changes in clocks and HTTP.

* Handle some review comments

* Update WASI implementations to avoid `as`

This can have a loss in precision so this shuffles around some types to
ensure that `try_into` and friends are always used instead of `as`. This
changes the source-of-truth for timestamps to be `i64` seconds so WASIp2
is the odd-one-out that can't represent negative timestamps.

* Flag expected WASI failures

* Get wasi:http tests working again

* Rename `proxy` module to `service` to reflect the WIT world.
* Adjust the middleware test to using the `middleware` world.

---------

Co-authored-by: Alex Crichton <[email protected]>

show more ...

Switch to using `wkg` for most WIT vendoring (#12327)

* feat(p3)!: vendor 0.3.0-rc-2026-01-06

Update wasmtime's WASI implementation from version
0.3.0-rc-2025-09-16 to 0.3.0-rc-2026-01-06, using wk

Switch to using `wkg` for most WIT vendoring (#12327)

* feat(p3)!: vendor 0.3.0-rc-2026-01-06

Update wasmtime's WASI implementation from version
0.3.0-rc-2025-09-16 to 0.3.0-rc-2026-01-06, using wkg for WIT vendoring.

This involves API changes in clocks and HTTP.

* ci: install wkg in monolith_checks

* Revert back to original WIT versions

Also refactor the script a bit to avoid too bash-isms and hopefully make
it a bit more straightforward what's happening.

---------

Co-authored-by: Bailey Hayes <[email protected]>

show more ...