chore(deps): lock file maintenance

[ferrlabs-renovate]

This PR contains the following updates:

Update	Change
lockFileMaintenance	All locks refreshed

🔧 This Pull Request updates lock files to use the latest dependency versions.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • "before 6am on monday"
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, 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]

Renovate lock-file-maintenance — Cargo.lock only, no Cargo.toml changes, so every bump stays within existing semver ranges.

What changed: Mostly routine patch/minor refreshes (uuid 1.25→1.26, indexmap 2.14.0→2.14.1, hyper 1.11.0→1.11.1, rtoolbox 0.0.5→0.0.6, windows-sys unified on 0.61.2). The one cluster worth flagging: secret-service 5.1.0→5.2.0 (the Linux keyring backend) pulled in the RustCrypto ecosystem's coordinated "hybrid-array" migration — aes 0.8→0.9, cipher 0.4→0.5, digest 0.10→0.11, hmac/hkdf 0.12→0.13, block-padding 0.3→0.4, inout 0.1→0.2, cbc 0.1→0.2 — where generic-array is dropped in favor of hybrid-array. These are breaking changes for direct consumers of those crates' APIs.

What breaks here: Nothing. None of aes/cipher/digest/hmac/hkdf/cbc/secret-service are direct dependencies — cli/Cargo.toml only pins sha2 = "0.11" directly, which is unaffected (stayed at 0.11.0). secret-service reaches this repo transitively through zbus-secret-service-keyring-store (cli/Cargo.toml:31, Linux-only), consumed solely via the keyring-core trait abstraction — no repo code touches the RustCrypto APIs directly.

CI: Check CLI and CI/Lint already passed against the regenerated lockfile (compiles clean), plus CI/Security, osv-scanner, snyk, gitleaks, zizmor, opengrep all green. CI/Test, RUSTSEC audit, and kind smoke test were still in progress at review time but nothing suggests they're at risk.

Uneventful bump — safe to merge once the remaining checks finish.