build: lock file maintenance (main)

[angular-robot]

This PR contains the following updates:

Update	Change
lockFileMaintenance	All locks refreshed

🔧 This Pull Request updates lock files to use the latest dependency versions.

---

• If you want to rebase/retry this PR, check this box

[angular-robot]

⚠️ 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: MODULE.bazel.lock

Command failed: bazel mod deps
2026/03/17 05:30:46 Downloading https://releases.bazel.build/8.6.0/release/bazel-8.6.0-linux-x86_64...
Extracting Bazel installation...
Starting local Bazel server (8.6.0) and connecting to it...
 no actions running
 no actions running
 no actions running
ERROR: Missing checksum for registry file https://bcr.bazel.build/modules/platforms/1.0.0/MODULE.bazel not permitted with --lockfile_mode=error. Please run `bazel mod deps --lockfile_mode=update` to update your lockfile.

[gemini-code-assist]

Code Review

This pull request contains automated updates to the pnpm-lock.yaml file, refreshing dependencies to their latest versions. The changes primarily consist of patch and minor version bumps, which is standard for lock file maintenance and helps keep dependencies current. The updates appear to be routine and I see no immediate issues with them.