chore(deps): update rust crate clap_complete to v4.6.10

[ferrlabs-renovate]

This PR contains the following updates:

Package	Type	Update	Change	Pending
clap_complete	dependencies	patch	4.6.9 → 4.6.10	4.6.11

---

Release Notes

clap-rs/clap (clap_complete)

v4.6.10

Compare Source

---

Configuration

📅 Schedule: (UTC)

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

🚦 Automerge: Enabled.

♻ 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.

[github-actions]

SonarQube — aucune nouvelle issue

_{Comparaison entre le projet bac à sable de cette PR et la branche par défaut : SonarQube Community n'analyse pas les PR, ce delta est calculé côté CI. Détail}

[ferrfleet]

clap_complete 4.6.9 → 4.6.10 is a patch bump with no documented changes upstream (empty changelog entry for 4.6.10). It depends only on clap, so there's nothing here that touches this repo's usage of the completion API.

Nit: the lockfile diff also re-resolves windows-sys from 0.61.2 → 0.52.0 for five unrelated crates (colored, errno, rustix, tempfile, winapi-util) — none of which relate to clap_complete. This is a valid resolution (cargo wrote the lockfile, so it satisfies those crates' semver ranges) and Test/Cargo Security are green, but it's worth noting this PR's CI never actually builds for x86_64/aarch64-pc-windows-msvc (that only happens in publish.yml at release time), so this particular version choice hasn't been exercised on Windows. Not blocking, just flagging the unrelated churn in case a future Windows release build hits something.

Coverage and Build Release Binary were still in progress at review time; both Linux-relevant jobs (Test, Cargo Security) and all security scans (osv-scanner, snyk, gitleaks, zizmor, opengrep) passed.