Bumped vitest.

[przemyslaw-zan]

🚀 Summary

Bumped vitest.

---

💡 Additional information

Coverage fell due to vitest changing method of calculating coverage.

---

Note

Medium Risk
Tooling-only change, but it touches the entire test/coverage stack and could cause widespread CI/test failures or coverage deltas due to Vitest v4 behavior changes.

Overview
Upgrades the repo-wide test runner from vitest v3 to v4 (and @vitest/coverage-v8), updating the lockfile accordingly.

Standardizes Vitest configs across packages by enabling stricter mock cleanup (clearMocks, mockReset, unstubEnvs, unstubGlobals with a few package-specific exceptions) and adjusting coverage settings (including new excludes and dropping coverage.all where it was set).

Updates a handful of tests/utilities to remain compatible with Vitest v4 mocking semantics, including making mockGetUserDependency() idempotent, removing manual cleanup hooks now handled by config, tightening assertions, and providing an explicit webpack mock implementation.

^{Written by Cursor Bugbot for commit fb20326. This will update automatically on new commits. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 2 potential issues.

^{Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.}