fix(deps): update minimal-versions for wasi

[xtqqczze]

Fix minimal version requirements for wasi and add a check to CI.

This also refactors the MSRV workflow configuration in CI by avoiding a matrix build, reducing GitHub Actions cache usage.

[NobodyXu]

Thank you

[xtqqczze]

@taiki-e Is there currently a better way to do this using cargo-minimal-versions? It seems like having support for generate-lockfile would be useful. This looks related to taiki-e/cargo-minimal-versions#17.

[taiki-e]

The correct approach is to call cargo-minimal-versions multiple times. Instead of simply calling generate-lockfile and then cargo-hack, cargo-minimal-versions performs various operations to avoid false negatives. generate-lockfile + cargo-hack, which does not accurately emulate this behavior, is always worse than cargo-minimal-versions. See https://github.com/taiki-e/cargo-minimal-versions#details for details.

[taiki-e]

--all-targets is usually a bad idea here since it enables dev-deps. This often hides compile errors that exist in lib/bin which will be released on crates.io. See also the quoted comment in https://github.com/taiki-e/cargo-minimal-versions#details.

[xtqqczze]

Is --no-dev-deps necessary with cargo-minimal-versions?

[taiki-e]

cargo-minimal-versions automatically do the same processing as --no-dev-deps when --all-targets/--tests/etc. are not used.

[xtqqczze]

@taiki-e Is there a way to run cargo minimal-versions check for multiple targets while resolving the minimal-version Cargo.lock only once?

[taiki-e]

Does multi-target (taiki-e/cargo-hack#167) not work?

[xtqqczze]

Does multi-target (taiki-e/cargo-hack#167) not work?

I didn't know about Cargo's multi-target builds! Since that feature was implemented in 1.64, we should be good to use it with our MSRV of 1.65.

[taiki-e]

Since that feature was implemented in 1.64

Btw, cargo-hack (used inside cargo-minimal-versions) emulates multi-target builds on pre-1.64 Rust (taiki-e/cargo-hack#168).