Option to disable "Testing types with tsc and vue-tsc is an experimental feature." logs

Clear and concise description of the problem

Right now, when you run with typecheck enabled, this warning is emitted:

https://github.com/vitest-dev/vitest/blob/b0b83e21424a9e9330c07b5f1d5ed82e01aa3f29/packages/vitest/src/node/config/resolveConfig.ts#L791-L795

Testing types with tsc and vue-tsc is an experimental feature.
Breaking changes might not follow SemVer, please pin Vitest's version when using it.

That's good to know when setting up the typecheck feature. But if a project is already using the feature, it can become kind of a lot. Especially in monorepos where multiple instances of Vitest get run.

Suggested solution

Could we have an option to say "yes, I know this is experimental, don't log"? Or at least only log once per system, determined by writing to a cache?

Alternative

...or stabilize the typecheck feature?

Additional context

Related:

• https://github.com/vitest-dev/vitest/issues/7773: filed last year, still awaiting triage
• https://github.com/flint-fyi/flint/issues/2398: we're in a monorepo with projects such that 33 of these logs are written upon every root-level pnpm test (😭)

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that requests the same feature to avoid creating a duplicate.

Start at packages/vitest/src/node/config/resolveConfig.ts around lines 791-795 and inspect how the typecheck warning is emitted. Define an option that suppresses the experimental-feature message while preserving the current default behavior, then add or update coverage for the logging behavior.