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 - "before 4am on monday" (UTC), 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 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 5 workspace projects
Progress: resolved 1, reused 0, downloaded 0, added 0
Progress: resolved 30, reused 0, downloaded 0, added 0
Progress: resolved 93, reused 0, downloaded 0, added 0
Progress: resolved 178, reused 0, downloaded 0, added 0
Progress: resolved 301, reused 0, downloaded 0, added 0
Progress: resolved 362, reused 0, downloaded 0, added 0
/tmp/renovate/repos/github/devsoc-unsw/ui-components/packages/eslint-config-custom:
 ERR_PNPM_UNSUPPORTED_ENGINE  Unsupported environment (bad pnpm and/or Node.js version)

This error happened while installing the dependencies of @typescript-eslint/eslint-plugin@8.58.0
 at @typescript-eslint/visitor-keys@8.58.0

Your Node version is incompatible with "eslint-visitor-keys@5.0.1".

Expected version: ^20.19.0 || ^22.13.0 || >=24
Got: 22.2.0

This is happening because the package's manifest has an engines.node field specified.
To fix this issue, install the required Node version.