chore(deps): update analog monorepo to v2.7.2

[ferrlabs-renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@analogjs/content (source)	2.7.1 → 2.7.2
@analogjs/platform (source)	2.7.1 → 2.7.2
@analogjs/router (source)	2.7.1 → 2.7.2

---

Warning

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

---

Release Notes

analogjs/analog (@​analogjs/content)

v2.7.2

Compare Source

Bug Fixes

• content: resolve fragment-only anchor hrefs against the current document, not (#​2501) (83d299a)
• vite-plugin-angular: preserve source maps across TypeScript transforms (#​2506) (cad322b)
• vite-plugin-angular: use null for default providedIn setting for Injectable (#​2515) (c555ba6)
• vite-plugin-nitro: exclude load-only server-function hosts (#​2543) (68d67c5)

---

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.

[ferrfleet]

Patch bump 2.7.1 → 2.7.2 for @analogjs/content, @analogjs/platform, @analogjs/router. Lockfile-only change, no package.json edits (both stay within the existing ^2.6.1 range).

Changelog is four bug fixes: content anchor-href resolution, vite-plugin-angular source-map preservation, vite-plugin-angular providedIn default, vite-plugin-nitro server-function host exclusion. No breaking changes, no new peer/runtime requirements. A repo-wide search found no use of the affected APIs (no server-function definitions, no explicit providedIn overrides), so none of these fixes touch code here.

CI was still mid-run at review time (several jobs in_progress/queued); nothing completed so far has failed. 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}