fix(worker): rpc listener leak when isolate: false

[AriPerkkio]

Description

• Fixes fix(pool): don't teardown the communication channel too soon if something is running after the test #8767 (comment)

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.
• Please check Allow edits by maintainers to make review process faster. Note that this option is not available for repositories that are owned by Github organizations.

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:.

[AriPerkkio]

Ideally this would be done after these 3 cleanups but not sure if there was some reason why it can't be done there..?

vitest/packages/vitest/src/runtime/worker.ts

Lines 67 to 71 in ede1f39

	finally {
	await rpcDone().catch(() => {})
	await Promise.all(cleanups.map(fn => fn())).catch(() => {})
	await environmentLoader?.close()
	}

The rpcDone should ensure rpc is, well, done.

[sheremet-va]

Ideally this would be done after these 3 cleanups but not sure if there was some reason why it can't be done there..?

Because there could be async processes that use the RPC (like fetch) started in tests. Closing the RPC hangs the process in these situations.

[AriPerkkio]

I wonder if that issue would come up in isolate: false too. The fetch started by previous test starts running when second test file is running. 🤔