Refresh Lockfiles

[shivros]

Description

Refreshes Cargo.lock with the latest semver-compatible dependency updates via cargo update, without changing any Cargo.toml constraints.

Motivation / context

• Pick up safe patch/minor fixes from the Rust ecosystem
• Reduce dependency drift and keep CI/runtime behavior current
• Keep risk low by limiting this PR to lockfile updates only

Environment note (Nix/direnv)

• If you use direnv + nix develop, your Rust version comes from the flake.
• With an older flake.lock, the dev shell may provide rustc 1.80.1, which fails after this lock refresh (indexmap 2.13.0 requires rustc >= 1.82).
• Ensure the dev shell uses a newer toolchain (for example by updating nixpkgs in flake.lock) or use a Rust toolchain >= 1.82.

Notable transitive upgrades

• tokio 1.39.3 -> 1.49.0
• mio 1.0.2 -> 1.1.1
• socket2 0.5.7 -> 0.6.2
• signal-hook 0.3.17 -> 0.3.18
• signal-hook-registry 1.4.2 -> 1.4.8
• bytes 1.7.1 -> 1.11.1
• futures-core 0.3.30 -> 0.3.31
• regex 1.10.6 -> 1.12.3

Dependencies required for this change: none (no new direct dependencies added).

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Validated locally after lockfile refresh:

cargo check
cargo test
make run

Also validated in Nix/direnv context (to confirm the Rust toolchain issue is resolved when using updated nixpkgs):

direnv exec . rustc --version
direnv exec . cargo check

Result

• cargo check: passed
• cargo test: passed (28 passed; 0 failed)
• direnv exec . cargo check: passed

Manually tested on Linux 6.18.7-arch1-1

[shivros]

@cyrinux Pretty safe. I would merge it but don't have write access.