fix!: remove Node types from the main entry point, use vitest/node instead

[sheremet-va]

Description

Closes #5481

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 vitest-dev ready!

Name	Link
🔨 Latest commit	173df0f
🔍 Latest deploy log	https://app.netlify.com/projects/vitest-dev/deploys/6855627055242500085f5b30
😎 Deploy Preview	https://deploy-preview-8200--vitest-dev.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[nvie]

@sheremet-va Would it be possible to backport this change to 3.2.x? We've been running into this issue from using @cloudflare/vitest-pool-workers (for which it's important that @types/node don't get imported as well).

[sheremet-va]

@sheremet-va Would it be possible to backport this change to 3.2.x? We've been running into this issue from using @cloudflare/vitest-pool-workers (for which it's important that @types/node don't get imported as well).

This is a breaking change, so we cannot backport it.