Update io-lifetimes, cap-std, and rsix (#3269)

- Fixes for compiling on OpenBSD

 - io-lifetimes 0.3.0 has an option (io_lifetimes_use_std, which is off
   by default) for testing the `io_safety` feature in Rust nightly.

crates/wasi-common/cap-std-sync/Cargo.toml

@@ -15,18 +15,18 @@ include = ["src/**/*", "README.md", "LICENSE" ]
 wasi-common = { path = "../", version = "0.29.0" }
 async-trait = "0.1"
 anyhow = "1.0"
-cap-std = "0.17.0"
-cap-fs-ext = "0.17.0"
-cap-time-ext = "0.17.0"
-cap-rand = "0.17.0"
-fs-set-times = "0.7.0"
-system-interface = { version = "0.11.0", features = ["cap_std_impls"] }
+cap-std = "0.18.0"
+cap-fs-ext = "0.18.0"
+cap-time-ext = "0.18.0"
+cap-rand = "0.18.0"
+fs-set-times = "0.9.0"
+system-interface = { version = "0.12.0", features = ["cap_std_impls"] }
 tracing = "0.1.19"
 bitflags = "1.2"
-io-lifetimes = { version = "0.2.3", default-features = false }
+io-lifetimes = { version = "0.3.0", default-features = false }
 
 [target.'cfg(unix)'.dependencies]
-rsix = "0.18.0"
+rsix = "0.20.4"
 
 [target.'cfg(windows)'.dependencies]
 winapi = "0.3"

crates/wasi-common/cap-std-sync/src/lib.rs

@@ -23,7 +23,7 @@
 //! is in the `Sched` abstraction. Once we can build an async scheduler based
 //! on Rust `Future`s, async impls will be able to interoperate, but the
 //! synchronous scheduler depends on downcasting the `WasiFile` type down to
-//! concrete types it knows about (which in turn impl `AsRawFd` for passing to
+//! concrete types it knows about (which in turn impl `AsFd` for passing to
 //! unix `poll`, or the analogous traits on windows).
 //!
 //! Why is this impl suffixed with `-sync`? Because `async` is coming soon!
@@ -31,6 +31,8 @@
 //! deps, so we will retain a sync implementation so that wasi-common users
 //! have an option of not pulling in an async runtime.
 
+#![cfg_attr(io_lifetimes_use_std, feature(io_safety))]
+
 pub mod clocks;
 pub mod dir;
 pub mod file;