fix(deps): update vite to >=7.3.6

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
vite@>=7.0.0 <=7.3.1 (source)	[>=7.3.2 → >=7.3.6](https://renovatebot.com/diffs/npm/vite@>=7.0.0 <=7.3.1/7.3.2/7.3.6)
vite@>=7.1.0 <=7.3.1 (source)	[>=7.3.2 → >=7.3.6](https://renovatebot.com/diffs/npm/vite@>=7.1.0 <=7.3.1/7.3.2/7.3.6)

---

Release Notes

vitejs/vite (vite@>=7.0.0 <=7.3.1)

v7.3.6

Compare Source

Please refer to CHANGELOG.md for details.

v7.3.5

Compare Source

Please refer to CHANGELOG.md for details.

v7.3.3

Compare Source

Please refer to CHANGELOG.md for details.

---

Configuration

📅 Schedule: (in timezone Europe/Berlin)

• Branch creation
  • "after 1am and before 5am every weekend"
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

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

---

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

---

This PR was generated by Mend Renovate. View the repository job log.

[github-actions]

Thank you for following the naming conventions! 🙏

[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

<--- Last few GCs --->

[908:0x2bbc9000]   114241 ms: Scavenge (reduce) (interleaved) 1488.6 (1510.5) -> 1488.6 (1511.2) MB, pooled: 0 MB, 8.88 / 0.00 ms  (average mu = 0.392, current mu = 0.424) allocation failure; 
[908:0x2bbc9000]   114300 ms: Mark-Compact (reduce) 1488.9 (1511.2) -> 1485.7 (1510.4) MB, pooled: 0 MB, 55.35 / 0.03 ms  (+ 1400.3 ms in 0 steps since start of marking, biggest step 0.0 ms, walltime since start of marking 1866 ms) (average mu = 0.395, cu

<--- JS stacktrace --->

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
----- Native stack trace -----

 1: 0xe46bbe node::OOMErrorHandler(char const*, v8::OOMDetails const&) [/opt/containerbase/tools/node/22.22.3/bin/node]
 2: 0x1243640 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [/opt/containerbase/tools/node/22.22.3/bin/node]
 3: 0x1243917 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [/opt/containerbase/tools/node/22.22.3/bin/node]
 4: 0x1472825  [/opt/containerbase/tools/node/22.22.3/bin/node]
 5: 0x1472853  [/opt/containerbase/tools/node/22.22.3/bin/node]
 6: 0x148b92a  [/opt/containerbase/tools/node/22.22.3/bin/node]
 7: 0x148eaf8  [/opt/containerbase/tools/node/22.22.3/bin/node]
 8: 0x1cf7681  [/opt/containerbase/tools/node/22.22.3/bin/node]
/usr/local/bin/node: line 18:   908 Aborted                 /opt/containerbase/tools/node/22.22.3/bin/node "$@"