Correctly resolve module paths when using Vite plugins that affect module resolution

[mrm007]

Fixes #1302.

The vite-node compiler now uses absolute paths internally, to avoid situations where a compilerOptions.baseUrl is defined and we incorrectly make paths root relative.

Other changes:

I had to upgrade the monorepo to TypeScript v5, but that doesn't have any effect on anything.

I moved tests from Vitest to Jest. Vitest has trouble correctly identifying and updating inline snapshots, but Jest handles them fine.

Probably easier to review some changes commit-by-commit.

[changeset-bot]

🦋 Changeset detected

Latest commit: 02db386

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 8 packages

Name	Type
@vanilla-extract/integration	Major
@vanilla-extract/vite-plugin	Patch
@vanilla-extract/esbuild-plugin-next	Patch
@vanilla-extract/esbuild-plugin	Patch
@vanilla-extract/jest-transform	Patch
@vanilla-extract/parcel-transformer	Patch
@vanilla-extract/rollup-plugin	Patch
@vanilla-extract/webpack-plugin	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[askoufis]

Good stuff 👏

Just some minor comments.