Unsafe multi-queue implementation

[inner-daemons]

Connections
Closes #8844

Description
Adds an unsafe multi-queue implementation. Very much a WIP

Testing
Nothing yet

Squash or Rebase?
Squash lmao

Checklist

• Run cargo fmt.
• Run taplo format.
• Run cargo clippy --tests. If applicable, add:
  • --target wasm32-unknown-unknown
• Run cargo xtask test to run tests.
• If this contains user-facing changes, add a CHANGELOG.md entry.

[inner-daemons]

For any future reviewers, this is what to pay special attention to IMO:

• Device::maintain
• Handling of when Device::get_queue() returns None (I don't have a good understanding of when this should happen or how to handle it, especially with more stuff living on the Queue now)
• Which stuff is made per-queue and which stuff should be (please consider this on your own as I probably missed some stuff)