fix: cleanup vitest in public resolveConfig API

[hi-ogawa]

Description

Currently we get a huge wall of logs like this https://github.com/vitest-dev/vitest/actions/runs/13711813132/job/38349623334?pr=7621#step:8:458

⎯⎯⎯⎯ Unhandled Rejection ⎯⎯⎯⎯⎯
Error: intentional unhandled rejection
 ❯ fixtures/unhandled-rejections/setup-unhandled-rejections.ts:2:42
 ❯ Object.setup fixtures/unhandled-rejections/setup-unhandled-rejections.ts:2:8
 ❯ TestProject._initializeGlobalSetup ../../packages/vitest/dist/chunks/cli-api.DIBEqC3b.js:10464:53
 ❯ Vitest.initializeGlobalSetup ../../packages/vitest/dist/chunks/cli-api.DIBEqC3b.js:12943:7
 ❯ ../../packages/vitest/dist/chunks/cli-api.DIBEqC3b.js:12854:9
 ❯ Vitest.runFiles ../../packages/vitest/dist/chunks/cli-api.DIBEqC3b.js:12883:12
 ❯ Vitest.start ../../packages/vitest/dist/chunks/cli-api.DIBEqC3b.js:12764:21
 ❯ startVitest ../../packages/vitest/dist/chunks/cli-api.DIBEqC3b.js:13910:7
 ❯ runVitest ../test-utils/index.ts:76:11

Some are due to test not doing proper cleanup. Also public resolveConfig API had hanging new Vitest, so I made it close properly.

I fixed all except these two https://github.com/vitest-dev/vitest/actions/runs/13712690144/job/38352041269?pr=7623#step:8:457, which can be reproduce by

pnpm -C test/config test run /unhandled /override
...
  Error: intentional unhandled rejection
  Error: intentional unhandled rejection

Probably this is due to error handler not cleaned up when resolve config is throwing. It should be fixed, but I guess we can deal with this later.

vitest/test/config/test/override.test.ts

Lines 304 to 306 in cad3d75

	await expect(async () => {
	await config(rawConfig.options)
	}).rejects.toThrowError(`Inspector host cannot be a URL. Use "host:port" instead of "${url}"`)

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