fix: add explicit vitest/vite resolution

[edisile]

Done

added explicit vitest/vite resolution to 7.3.2 (vitest 4.1.3 installs vite 8 as a dependency and might lead to issues, as pointed out by copilot here)

How to QA

• check that demo runs
• check that CI is green

Testing

• This PR has tests
• No testing required (explain why):

Security

• Security considerations for review (list them):
  • Examples:
  • Access control: users can only access their own data
  • Input: user input is validated and sanitised
  • Sensitive data: secret or private data is not exposed in any way
  • ...
• This PR has no security considerations (explain why):

Issue / Card

Fixes #

Screenshots

UX Approval

• This PR does not require UX approval
• This PR does require UX approval (add context):

[webteam-app]

Demo

Jenkins

demos.haus

[Copilot]

Pull request overview

Pins Vitest’s transitive Vite dependency to the repo’s Vite 7 baseline to avoid Vitest pulling in Vite 8, keeping the frontend toolchain consistent for builds and tests.

Changes:

• Add a Yarn resolution to force vitest → vite to 7.3.2.
• Update yarn.lock to remove the Vite 8 subtree and dedupe to Vite 7.3.2.

Reviewed changes

Copilot reviewed 1 out of 2 changed files in this pull request and generated 1 comment.

File	Description
package.json	Adds resolutions.vitest/vite = 7.3.2 to prevent Vitest from installing Vite 8.
yarn.lock	Reflects the resolution by collapsing Vite to 7.3.2 and removing Vite 8-related transitive deps.