refactor!: remove exporting internal APIs

[bluwy]

Description

• Remove internal APIs from config.ts: isDepsOptimizerEnabled and getDepOptimizationConfig
• Export the types explicitly from config.ts
• Rename ResolveWorkerOptions to ResolvedWorkerOptions (it was bugging me)
• Remove internal types from ./optimizer

NOTE:

• The removed internal type DepOptimizationOptions is only referenced via DepOptimizationOptions (exported), but I don't think it needs to also be exported. used by vitest
• The removed internal type DepsOptimizer is only referenced at

  vite/packages/vite/src/node/plugins/resolve.ts

  Line 118 in 62ae743

  getDepsOptimizer?: (ssr: boolean) => DepsOptimizer | undefined

  , but I don't think that's an option users should use anyways.

Also it's odd that we export InternalResolveOptions and most props there are actually internal too.

Additional context

---

What is the purpose of this pull request?

• Bug fix
• New Feature
• Documentation update
• Other

[sapphi-red]

it's odd that we export InternalResolveOptions and most props there are actually internal too.

The reason was because createResolver in ResolvedConfig uses InternalResolveOptions and api-extractor shows an warning if we don't export InternalResolveOptions.

[sapphi-red]

/ecosystem-ci run

[vite-ecosystem-ci]

📝 Ran ecosystem CI: Open

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

[sapphi-red]

LGTM 👍
It would be nice to add this to https://github.com/vitejs/vite/blob/main/docs/guide/migration.md#advanced.