fix(vitest): remove excessive listeners when running without isolation, don't reset the state

[sheremet-va]

Description

We don't reset the state anymore because it doesn't do anything (the state is on the global object, so resetting the reference makes no difference for gc). The same can be said for the environment.

I also noticed Vitest sometimes shows a warning that too many listeners are applied - I think we worked around it by silencing the error with setMaxListeners which should never be the solution 😄

Closes #5071

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

• It's really useful if your PR references an issue where it is discussed ahead of time. If the feature is substantial or introduces breaking changes without a discussion, PR might be closed.
• Ideally, include a test that fails without this PR but passes with it.
• Please, don't make changes to pnpm-lock.yaml unless you introduce a new test example.

Tests

• Run the tests with pnpm test:ci.

Documentation

• If you introduce new functionality, document it. You can run documentation with pnpm run docs command.

Changesets

• Changes in changelog are generated from PR name. Please, make sure that it explains your changes in an understandable manner. Please, prefix changeset messages with feat:, fix:, perf:, docs:, or chore:.

[netlify]

✅ Deploy Preview for fastidious-cascaron-4ded94 canceled.

Name	Link
🔨 Latest commit	95a90f1
🔍 Latest deploy log	https://app.netlify.com/sites/fastidious-cascaron-4ded94/deploys/65c35e14beed8c0008a0e074