feat(deps)!: upgrade to vitest v4

[danielroe]

🔗 Linked issue

resolves #1482
resolves #1518

❓ Type of change

• 📖 Documentation (updates to the documentation or readme)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality)
• ✨ New feature (a non-breaking change that adds functionality)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

this updates us to vitest v4 and drops support for previous versions of vitest.

there's still an issue with starting vitest programmatically (in the nuxt devtools) but it's unclear to me if this is a nuxt/test-utils bug or a vitest one (resolved in #1524)

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/@nuxt/test-utils@1481

commit: 5395301

[OrbisK]

There is a problem with runtime config:

  runtimeConfig: {
    public: {
      whatever: {
        hello: 'world',
      },
    },
  },

  it('renders', () => {
    const config = useRuntimeConfig()
    console.log('public', config.public)
  })

public {}

Reproduction: https://github.com/OrbisK/test-utils-fork/tree/feat/vitest-4-reprod-runtimeconfig

[danielroe]

@OrbisK it was a typo by me! now fixed in bcef5e9.