chore(deps): update rust crate tokio to v1.53.2

[ferrlabs-renovate]

This PR contains the following updates:

Package	Type	Update	Change
tokio (source)	workspace.dependencies	patch	1.53.1 → 1.53.2

---

Release Notes

tokio-rs/tokio (tokio)

v1.53.2: Tokio v1.53.2

Compare Source

1.53.2 (October 3rd, 2026)

Fixed

• fs: handle integer overflow in buffered relative seek (#​8574)
• io: revert "always cleanup AsyncFd registration list on deregister" (#​8540)
• process: unregister Windows wait before closing child handle (#​8564)
• rt: drop blocking pool mutex before shutting down rejected task (#​8562)
• sync: fix mpsc index wraparound in block reclamation (#​8546)
• sync: forget mpsc Permit before sending value (#​8560)
• sync: validate MAX_PERMITS in Semaphore::acquire (#​8548)
• sync: wake broadcast Sender::closed outside mutex (#​8558)
• task: drop replaced waker outside lock in JoinSet (#​8554)
• time: drop timer lock before dropping waker in clear_entry (#​8552)
• time: expire timers directly on shutdown without rotating wheel (#​8570)

Fixed (unstable)

• fs: clamp io_uring read length to u32::MAX (#​8572)
• rt: ignore current_thread task dumps from other runtimes (#​8544)
• rt: preserve io_uring context if a completion waker panics (#​8566)
• sync: fix semaphore use-after-free and permit leak on tracing panic (#​8542)
• taskdump: restore deferred leaf wakes during capture (#​8445)
• time: drop stored waker when cancelling alt timer entry (#​8550)

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate CLI.

[ferrfleet]

tokio 1.53.1 -> 1.53.2 is a patch bump. Nothing blocking.

Nit: the lockfile also changes crates that have nothing to do with tokio. Sixteen packages move off windows-sys 0.60.2 onto 0.52.0, 0.59.0 or 0.61.2. quinn and quinn-udp go from socket2 0.6.5 down to 0.5.10. All of these are still inside their semver ranges, so the build should be fine. But it means more duplicate copies of windows-sys and socket2 in the tree, and quinn gets an older socket2. It looks like the lockfile was re-resolved rather than updated with a targeted cargo update -p tokio. To keep the diff to tokio only, regenerate it that way.

CI was still running (build, Coverage, compose, desktop-csp) when I reviewed.