feat: optimize deps option to turn off auto discovery

[patak-dev]

Description

Edit: I ended up renaming it to noDiscovery.

Adds a new experimental boolean option optimizeDeps.noDiscovery, defaulting to true

  /*
   * Automatic dependency discovery. When `noDiscovery` is true, only dependencies 
   * listed in `include` will be optimized. The scanner isn't run for cold start 
   * in this case. CJS-only dependencies must be present in `include` during dev.
   * @default false
   * @experimental
   */
  noDiscovery?: boolean

@sheremet-va is exploring replacing Vitest deps.inline feature with Vite's deps optimization. To make this work, they need auto-discovery of dependencies to be turned off. They would like to have full control of what dependencies get optimized using optimizeDeps.include. We should also merge #12414 to add glob support to optimizeDeps.include

Some other options we evaluated in this gist.

Edit: scratch the next paragraph, as it simplified the logic to rename at the end.
@bluwy also proposed we use noDiscovery instead of autoDiscovery so we can have the option be false by default. I think this is a good idea in general but in this case, I find it a bit more confusing. @bluwy I checked and we have a lot of boolean options that default to true. preTransformRequests for example. Let's see what others think.

It is experimental because @sheremet-va will need to play with this and we may end up changing this feature later. I think we could move forward so they can check what we are missing.

---

What is the purpose of this pull request?

• Bug fix
• New Feature
• Documentation update
• Other

[stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[antfu]

LGTM! 👍

I wouldn't worry about the default true/false much, as long as we provide jsdocs and documentation. I understand that making options opt-in would be a good design pattern for understanding, but I feel that only work if all the options are falsy default (that might need to whole set of breaking changes)

[patak-dev]

I think the same @antfu. In the end, I switched this one to noDiscovery because if not we would be forced to have new types for resolved Optimize Deps Options, and the logic when using the option was negated all the time.

[sheremet-va]

I like this 👍🏻 Thank you 🙏🏻

Vitest probably cannot remove inline for some time now, but if this feature will be more performant then we can recommend it over inline 👍🏻

[bluwy]

Nice tests!

[patak-dev]

Starting discussion to stabilize this feature:

• Stabilizing `optimizeDeps.noDiscovery` #13814