chore(deps): update dependency vite to v5.2.9

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
vite (source)	5.2.8 -> 5.2.9

---

Release Notes

vitejs/vite (vite)

v5.2.9

Compare Source

• fix: fsp.rm removing files does not take effect (#​16032) (b05c405), closes #​16032
• fix: fix accumulated stacks in error overlay (#​16393) (102c2fd), closes #​16393
• fix(deps): update all non-major dependencies (#​16376) (58a2938), closes #​16376
• chore: update region comment (#​16380) (77562c3), closes #​16380
• perf: reduce size of injected __vite__mapDeps code (#​16184) (c0ec6be), closes #​16184
• perf(css): only replace empty chunk if imported (#​16349) (e2658ad), closes #​16349

---

Configuration

📅 Schedule: Branch creation - "after 5:00am every weekday, before 7:00am every weekday,every weekend" (UTC), Automerge - "before 7am every weekday" (UTC).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

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

---

This PR has been generated by Mend Renovate. View repository job log here.

[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: driver-adapters-wasm/neon-cfpages-remix/pnpm-lock.yaml

 ERR_PNPM_UNSUPPORTED_ENGINE  Unsupported environment (bad pnpm and/or Node.js version)

Your pnpm version is incompatible with "/tmp/renovate/repos/github/prisma/ecosystem-tests".

Expected version: 8
Got: 9.0.4

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

To install the latest version of pnpm, run "pnpm i -g pnpm".
To check your pnpm version, run "pnpm -v".