use Rust stable

[aviramha]

Tracking issue for things that we need to be stable in Rust so we can stop using nightly.
Overall I think we should seek to avoid introducing any more nightly features.

• Tracking Issue for RFC 3028: Allow "artifact dependencies" on bin, cdylib, and staticlib crates rust-lang/cargo#9096
• Tracking issue for RFC 2137: Support defining C-compatible variadic functions in Rust  rust-lang/rust#44930
• once_cell - can remove after nightly-2023-05-24 doesn't compile #1457 I think
• Tracking Issue for result_option_inspect rust-lang/rust#91345 - It seems from the discussion it will never be stable, and maybe we should use https://docs.rs/tap/latest/tap/
• Tracking issue for RFC 2632, impl const Trait for Ty and ~const (tilde const) syntax rust-lang/rust#67792
• naked functions - couldn't find a tracking issue for stabilisation of it?
• Tracking Issue for Result::flatten (result_flattening) rust-lang/rust#70142
• #![feature(io_error_uncategorized)] couldn't find that we use that actually?
• Tracking issue for eRFC 2497, "if- and while-let-chains, take 2" rust-lang/rust#53667
• Tracking issue for #![feature(async_closure)] (RFC 2394) rust-lang/rust#62290
• Tracking Issue for try_trait_v2, A new design for the ? desugaring (RFC#3058) rust-lang/rust#84277
• Tracking Issue for ops::Residual (feature try_trait_v2_residual) rust-lang/rust#91285
• Tracking issue for trait aliases rust-lang/rust#41517
• Tracking Issue for #![feature(c_size_t)] (std::os::raw::c_size_t/std::os::raw::c_ssize_t) rust-lang/rust#88345
• Tracking Issue for pointer_bytes_offsets rust-lang/rust#96283
• is_some_and - stable! need to upgrade to 1.70
• Tracking Issue for async_fn_in_trait, return_position_impl_trait_in_trait rust-lang/rust#91611