Add onCleanup hook

[sheremet-va]

Clear and concise description of the problem

There are times when the test runners needs to run a cleanup callback manually and not tied it to the test runner lifecycle (avoid beforeEach/afterEach). A good example of this is calling the cleanup when switching tests in the Browser Mode UI.

Suggested solution

@vitest/runner can expose an onCleanup hook. Consumers of the runner can decide when to run passed down callbacks. By default, Vitest will run those callbacks after each test (when running tests in the Node.js environment). Vitest Browser Mode will also run those hooks after each test, except for the last one, so the UI is still available.

Alternative

No response

Additional context

See #7141 for more details

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

[hi-ogawa]

I think this was another browser mode specific hack for "cleanup".

vitest/packages/browser/src/client/tester/runner.ts

Lines 41 to 44 in 8f13825

	onBeforeTryTask: VitestRunner['onBeforeTryTask'] = async (...args) => {
	await userEvent.cleanup()
	await super.onBeforeTryTask?.(...args)
	}

I actually don't remember well why we need this in two places, but there was something tricky with resetting playwright instance's state between multiple test files.

vitest/packages/browser/src/client/tester/tester.ts

Lines 151 to 153 in 8f13825

	// need to cleanup for each tester
	// since playwright keyboard API is stateful on page instance level
	await userEvent.cleanup()