chore(deps): lock file maintenance

[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: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) (UTC), Automerge - At any time (no schedule defined).

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

♻ Rebasing: Whenever PR becomes conflicted, 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 was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml

Scope: all 3 workspace projects
Progress: resolved 1, reused 0, downloaded 0, added 0
Progress: resolved 45, reused 0, downloaded 0, added 0
Progress: resolved 88, reused 0, downloaded 0, added 0
Progress: resolved 91, reused 0, downloaded 0, added 0
Progress: resolved 94, reused 0, downloaded 0, added 0
Progress: resolved 178, reused 0, downloaded 0, added 0
Progress: resolved 287, reused 0, downloaded 0, added 0
Progress: resolved 340, reused 0, downloaded 0, added 0
Progress: resolved 385, reused 0, downloaded 0, added 0
Progress: resolved 481, reused 0, downloaded 0, added 0
Progress: resolved 565, reused 0, downloaded 0, added 0
Progress: resolved 606, reused 0, downloaded 0, added 0
Progress: resolved 610, reused 0, downloaded 0, added 0
Progress: resolved 658, reused 0, downloaded 0, added 0
Progress: resolved 693, reused 0, downloaded 0, added 0
Progress: resolved 825, reused 0, downloaded 0, added 0
Progress: resolved 930, reused 0, downloaded 0, added 0
Progress: resolved 1009, reused 0, downloaded 0, added 0
Progress: resolved 1066, reused 0, downloaded 0, added 0
 WARN  Request took 14951ms: https://registry.npmjs.org/vite
Progress: resolved 1124, reused 0, downloaded 0, added 0
Progress: resolved 1143, reused 0, downloaded 0, added 0
Progress: resolved 1154, reused 0, downloaded 0, added 0
Progress: resolved 1167, reused 0, downloaded 0, added 0
Progress: resolved 1197, reused 0, downloaded 0, added 0
Progress: resolved 1225, reused 0, downloaded 0, added 0
Progress: resolved 1313, reused 0, downloaded 0, added 0
Progress: resolved 1319, reused 0, downloaded 0, added 0
Progress: resolved 1468, reused 0, downloaded 0, added 0
Progress: resolved 1565, reused 0, downloaded 0, added 0
Progress: resolved 1698, reused 0, downloaded 0, added 0
Progress: resolved 1879, reused 0, downloaded 0, added 0
 ERR_PNPM_TRUST_DOWNGRADE  High-risk trust downgrade for "semver@5.7.2" (possible package takeover)

This error happened while installing the dependencies of @nuxtjs/eslint-config-typescript@12.1.0
 at @nuxtjs/eslint-config@12.0.0
 at eslint-plugin-unicorn@44.0.2
 at read-pkg-up@7.0.1
 at read-pkg@5.2.0
 at normalize-package-data@2.5.0

Trust checks are based solely on publish date, not semver. A package cannot be installed if any earlier-published version had stronger trust evidence. Earlier versions had provenance attestation, but this version has no trust evidence. A trust downgrade may indicate a supply chain incident.