refactor(types): bundle client types

[sapphi-red]

Description

Moved d.ts files under types to src/dep-types and src/types and use api-extractor to bundle client types.

This solves following issues:

• prevent inconsistency between 'vite' and 'types/*'
  • fix(types): mark explicitImportRequired optional and experimental #9962
  • fix(types): add missing options parameter to importMeta #6433, fix(types): dynamic import in import.meta #6456, fix: avoid referencing importGlob from importMeta.d.ts #6531
• types directory is not included in exports field but was included in package
  • it was not clear whether this is intended to be exported
• types directory included dep types and it was a bit hard to differentiate types of deps or not
• fixes fix: Use lower case filenames for types so they can be imported correctly on Linux #9827
  • Now vite/types/importMeta can be imported by vite/import-meta or import ViteImportMeta type from vite/client/types

This PR deprecates:

• import 'vite/types/*'
  • Use import 'vite/client/types' or import 'vite'
• import { /* import.meta.glob related types */ } from 'vite' (related: vite config files can't be compiled without dom types #9813)
  • Use import 'vite/client/types'

I added facade files under types directory so there should be backward compatibility.

Additional context

https://vitejs.dev/guide/api-plugin.html#typescript-for-custom-events
This example was not working for server.ws.send('custom:foo', { msg: 'foo' }). So I updated the docs.

---

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

[patak-dev]

/ecosystem-ci run

[vite-ecosystem-ci]

📝 Ran ecosystem CI: Open

suite	result
astro	✅ success
iles	✅ success
ladle	✅ success
laravel	✅ success
marko	✅ success
nuxt-framework	✅ success
rakkas	✅ success
storybook	❌ failure
svelte	✅ success
vite-plugin-ssr	✅ success
vite-setup-catalogue	✅ success
vitepress	❌ failure
vitest	✅ success
windicss	✅ success

[patak-dev]

Amazing work @sapphi-red! I think to play safe it is better to merge this one on the 3.2 beta, and we could delete the facade in v4.

[sapphi-red]

/ecosystem-ci run

[vite-ecosystem-ci]

📝 Ran ecosystem CI: Open

suite	result
astro	✅ success
iles	✅ success
ladle	✅ success
laravel	✅ success
marko	✅ success
nuxt-framework	✅ success
rakkas	✅ success
storybook	❌ failure
svelte	✅ success
vite-plugin-ssr	✅ success
vite-setup-catalogue	✅ success
vitepress	✅ success
vitest	✅ success
windicss	✅ success

[sapphi-red]

When vite/client or vite/import-meta is used from a file using moduleResolution: "nodenext", this import needs to be vite/client/types or vite/client/types.js... (vitepress uses moduleResolution: "nodenext")

[Princesseuh]

Tried this PR inside Astro to see if it fixed #9827 and everything worked 👍 Nice work!

[sapphi-red]

/ecosystem-ci run

[vite-ecosystem-ci]

📝 Ran ecosystem CI: Open

suite	result
astro	✅ success
iles	✅ success
ladle	❌ failure
laravel	❌ failure
marko	✅ success
nuxt-framework	✅ success
rakkas	✅ success
storybook	✅ success
svelte	✅ success
vite-plugin-ssr	✅ success
vite-setup-catalogue	✅ success
vitepress	✅ success
vitest	✅ success
windicss	✅ success