A change in Rust nightly features broke version 0.2.5 of the `cstr`
crate, whose nightly-only features are enabled in some examples. The
breakage was quickly fixed upstream in the 0.2.6 version, this updates
the locks.
The riotmodules dependency was missed in bc8ec6d5, and while generally
it does not severly harm builds, it does harm builds riotdocker CI where
branches are switched, which is blocked by dirty files in the checkout.
The riot-wrappers version was missed when what is now 5e75f4bd was
rebased onto fdc4e11a.
Examples have previously relied on the (really: some) nightly toolchain
to be the default. As that, in practice, is a problematic assumption,
the latest toolchain to use is now determined programmatically, and that
is set explicitly on the examples that use nightly.
Workaround-For: https://github.com/rust-lang/rustup/issues/3015
This is not so much an update (riot-wrappers stays at the same commit,
riot-sys just advances by one that re-enables an optional dependency,
but of course third party crates are updated) but more reflects the
switch from using released crates to git versions.
Updating to riot-sys 0.7.7 enables support for more recent C2Rust
versions, and to riot-wrappers 0.7.22 unblocks [17990].
[17990]: https://github.com/RIOT-OS/RIOT/pull/17990
This restores compatibility with current nightlies by using the latest
coap-message version (after a nightly-only feature that uses saw a late
change), and also removes obstacles for use with stable Rust 1.59 (in
unrelated parts; the CoAP example is still nightly-only).
Contributes-To: https://github.com/RIOT-OS/RIOT/issues/17526
This pulls in adjustments to the C-nonbreaking but Rust-breaking API
change in https://github.com/RIOT-OS/RIOT/pull/17359
cstr_core is forcibly kept at 0.2.4 because 0.2.5 needs a newer nightly
than riotdocker currently has.
