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

[ferrlabs-renovate]

This PR contains the following updates:

Package	Type	Update	Change
tokio (source)	dependencies	patch	1.53.2 → 1.53.3

---

Release Notes

tokio-rs/tokio (tokio)

v1.53.3: Tokio v1.53.3

Compare Source

1.53.3 (October 13th, 2026)

Added

• io: add AsyncFd::register and AsyncFd::register_with_interest (#​8587)

Changed

• io: deprecate AsyncFd::{new, with_interest, try_new, try_with_interest} (#​8587)

Fixed

• io: wake and drop DuplexStream wakers outside the lock (#​8618)
• macros: avoid unreachable_code in join! and try_join! for Infallible (#​8518)
• runtime: fix paused time auto-advancing when I/O wakes a task on current_thread (#​8595)
• sync: wake waiters outside the lock when closing a semaphore (#​8529)
• test: fix several flaky tests (#​8196, #​8427, #​8609)

Fixed (unstable)

• rt: keep io_uring op alive when submission fails after push (#​8185)

---

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-interne]

tokio 1.53.2 → 1.53.3 patch bump, lockfile only. Looks fine.

Nit: the re-resolve also moved six crates (errno, rustix, tempfile and others) from windows-sys 0.61.2 to 0.52.0. Both versions were already in the lock and their declared ranges allow it, so it's valid, but it only affects Windows targets and CI here doesn't build for Windows. If the churn bothers you, cargo update -p windows-sys@0.52.0 --precise ... won't undo it cleanly; regenerating with cargo update -p tokio alone from main should.