chore(deps): update rust crate clap to v4.6.7

[ferrlabs-renovate]

This PR contains the following updates:

Package	Type	Update	Change
clap	dependencies	patch	4.6.6 → 4.6.7

---

Release Notes

clap-rs/clap (clap)

v4.6.7

Compare Source

Features

• (derive) Add #[command(defer = <bool>)] attribute to opt-in to lazy initialisation of subcommands

---

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 4.6.6 → 4.6.7, patch bump, Cargo.lock only. Changelog lists a single addition: an opt-in #[command(defer = <bool>)] derive attribute for lazy subcommand init. No removals, renames, or default changes. clap_derive also moves to 4.6.7 in lockstep, as expected.

Nothing in this repo touches the new attribute, so there's nothing to break. The lockfile also resolves several unrelated crates (redox_users, rustix, getrandom, etc.) down to windows-sys 0.52.0 from 0.61.2 — that's normal dependency-graph churn from a lockfile regen, not something clap caused, and both are pre-existing entries in the lock file rather than a new pin.

CI was still mid-run at review time (Test, Build, Coverage, Cargo Security in progress) with nothing failed so far. Uneventful bump, approving.