fix: resolve "vite" relative to the project root instead of using a dependency, if possible

[sheremet-va]

Description

The goal is to avoid any breaking changes even with the most unhinged solutions

Turns out we cannot use TLA because it taints the whole module graph, meaning user dependencies in the config can't be loaded, for example (even require(vite)). I assumed that it doesn't affect siblings imports previously.

Testing simple use cases with vite 6, vite 7 and vite 8 seems to work (including Node 20 without require(esm) support).

The exports tests should be fixed with antfu/vitest-package-exports#5 because require(esm) cannot be imported in Promise.all() 🤷

[pkg-pr-new]

@vitest/browser

npm i https://pkg.pr.new/@vitest/browser@9586

@vitest/browser-playwright

npm i https://pkg.pr.new/@vitest/browser-playwright@9586

@vitest/browser-preview

npm i https://pkg.pr.new/@vitest/browser-preview@9586

@vitest/browser-webdriverio

npm i https://pkg.pr.new/@vitest/browser-webdriverio@9586

@vitest/coverage-istanbul

npm i https://pkg.pr.new/@vitest/coverage-istanbul@9586

@vitest/coverage-v8

npm i https://pkg.pr.new/@vitest/coverage-v8@9586

@vitest/expect

npm i https://pkg.pr.new/@vitest/expect@9586

@vitest/mocker

npm i https://pkg.pr.new/@vitest/mocker@9586

@vitest/pretty-format

npm i https://pkg.pr.new/@vitest/pretty-format@9586

@vitest/runner

npm i https://pkg.pr.new/@vitest/runner@9586

@vitest/snapshot

npm i https://pkg.pr.new/@vitest/snapshot@9586

@vitest/spy

npm i https://pkg.pr.new/@vitest/spy@9586

@vitest/ui

npm i https://pkg.pr.new/@vitest/ui@9586

@vitest/utils

npm i https://pkg.pr.new/@vitest/utils@9586

vitest

npm i https://pkg.pr.new/vitest@9586

@vitest/web-worker

npm i https://pkg.pr.new/@vitest/web-worker@9586

@vitest/ws-client

npm i https://pkg.pr.new/@vitest/ws-client@9586

commit: 63fa6f3

[sheremet-va]

Superseded by a much simpler fix at #9587