chore(deps): lock file maintenance

[ferrlabs-renovate]

This PR contains the following updates:

Update	Change
lockFileMaintenance	All locks refreshed

---

Warning

Some dependencies could not be looked up. Check the warning logs for more information.

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

Lock file maintenance only, no manifest/version-range changes.

Cargo.lock: all patch bumps on transitive deps (syn 3.0.4→3.0.5, cc, find-msvc-tools, ipnet, js-sys, wasm-bindgen family, tokio-rustls, portable-atomic-util). Nothing here is a direct dependency exercising a documented breaking change.

pnpm-lock.yaml: same pattern, patch/point bumps in the Angular/Analog site tooling (browserslist, postcss, pkg-types, rc9, etc.) plus a couple of resolution-hash-only diffs (@angular/build content hash, picomatch split to 4.0.5/4.0.7 for different consumers). No dependency range changed in package.json.

CI: no failing check runs at time of review (several still in progress — Check, Coverage, git-lfs bundled jobs — but nothing red so far). Nothing blocking.

[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}