fix!: put manifest files in .vite directory by default

[sapphi-red]

Description

Changes the default output path of manifest/ssrManifest to .vite/manifest.json/.vite/ssr-manifest.json.

fixes #9636

Additional context

---

What is the purpose of this pull request?

• Bug fix
• New Feature
• Documentation update
• Other

Before submitting the PR, please make sure you do the following

• Read the Contributing Guidelines.
• Read the Pull Request Guidelines and follow the PR Title Convention.
• Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
• Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
• Ideally, include relevant tests that fail without this PR but pass with it.

[stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[sapphi-red]

/ecosystem-ci run

[vite-ecosystem-ci]

📝 Ran ecosystem CI: Open

suite	result
analogjs	✅ success
astro	✅ success
histoire	❌ failure
ladle	❌ failure
laravel	✅ success
marko	✅ success
nuxt	❌ failure
nx	✅ success
previewjs	✅ success
qwik	✅ success
rakkas	❌ failure
sveltekit	✅ success
unocss	✅ success
vite-plugin-pwa	✅ success
vite-plugin-ssr	❌ failure
vite-plugin-react	✅ success
vite-plugin-react-pages	❌ failure
vite-plugin-react-swc	✅ success
vite-plugin-svelte	❌ failure
vite-plugin-vue	❌ failure
vite-setup-catalogue	✅ success
vitepress	✅ success
vitest	✅ success

[Brain2000]

This just broke our build where the vite manifest was expected to be in the root folder, and we are still on 4.3.3. Weird...

[Brain2000]

It looks like pnpm dlx isn't using the package.json file for vite, so somehow it is using version 5.0.0 instead of 4.3.3....
npx vite shows version 4.3.3
pnpm dlx vite shows version 5.0.0

At least now I know where this is coming from...

[gcaraciolo]

this pr introduces a bug in inertia-laravel in production. https://github.com/inertiajs/inertia-laravel

Inertia expects manifest.json to be at public/build. a quick fix was to provide this path in vite.config

[bluwy]

@gcaraciolo you should report the issue to the repo. This is an intended breaking change in Vite 5.