treewide: Update Rust dependencies

[chrysn]

Contribution description

This updates riot-sys and riot-wrappers, as well as other Rust dependencies.

See issue references for what changes in our crates; outside that, none of the updates stand out particularly. (There are some auto-updates around proc-macro and Unicode, but that's just host side tooling).

Testing procedure

CI build testing should suffice.

Issues/PRs references

Complete list of PRs pulled in to this in our crates:

• riot-sys:
  • headers: Don't let C2Rust process xtimer rust-riot-sys#51
  • headers: Add nimble_autoadv rust-riot-sys#52
  • build: Add more bindgen-Debug exceptions for nimble 1.8 rust-riot-sys#53
  • headers: Add ztimer64 rust-riot-sys#54
• riot-wrappers:
  • Added UART module (UART wrapper (chrysn's cleanup) rust-riot-wrappers#143, originally by @kbarning, with help from @Teufelchen1)
  • Added SPI wrappers (spi: Add new embedded-hal 1.0 interface rust-riot-wrappers#141)
    • [edit] Fixes from spi: Tolerate platforms defining their enums differently rust-riot-wrappers#144
  • Error preparations (Error enhancements rust-riot-wrappers#128)
  • Build system enhancements (build: Acknowledge all available periph_uart variations rust-riot-wrappers#137, Minor fixes in build script and formatting rust-riot-wrappers#140)
  • Documentation and CI fixes (doc: Update URI rust-riot-wrappers#136, deny: Allow newer Unicode license rust-riot-wrappers#138, Add contributing guide rust-riot-wrappers#139)
  • Typos (msg: Typo fix rust-riot-wrappers#142)

[Teufelchen1]

That's a lot of dependencies.

[riot-ci]

Murdock results

✔️ PASSED

5d7bff8 treewide: Update riot-sys

Success	Failures	Total	Runtime
10271	0	10271	22m:16s

Artifacts

• Documentation preview

[chrysn]

CI said no; apparently, SPI clocks are odd somewhere.

That's a lot of dependencies.

Yes it is. It makes sense to take a more fine-grained viewpoint, though:

• Many of those in Cargo.lock don't even show up in the Cargo tree (ie. they have no way of influencing the build): For example, windows-sys gets pulled in through libc and errno, but only when building on Windows.
• Many that do show up in the cargo tree are build tools, eg. bindgen. In other environments than cargo, we might just require a CLI tool to be installed and have the build system call out to it. On Rust, it is common for build.rs to just pull in a crate for that – both making it convenient for the user to not have to install an extra tool (like c2rust where sadly that all doesn't work) and for us to have good control of when things may break, but on the downside those are all listed as dependencies.
• A cargo tree --edges normal still shows a lot of crates, but of a more managable size. Many of those are interface-only crates (embedded-graphics, embedded-hal, coap-message, switch-hal, mutex-trait) – we could make those optional, but given they are rather cheap for all other aspects than the list, that'd just make maintenance harder.
  • Besides riot-wrappers, also coap-handler-implementations pulls in such a swath of (partially old, even dangerous) interfaces (eg. multiple versions of minicbor). They don't do anything (no code emitted from there) unless someone else comes with "hey I have data from that library, please send it", but once more, making all them optional would put an otherwise useless load on maintenance.

[chrysn]

This can be unblocked by RIOT-OS/rust-riot-wrappers#144, which needs to be merged before I can unblock this PR.

[chrysn]

The last patch updates riot-sys only to address the previous build failures.