See associated pull request for more information.

See associated pull request for more information.

See associated pull request for more information.

See associated pull request for more information.

…g is used

When a Vitest configuration file is provided via the `runnerConfig` option,
the builder now only validates that the `vitest` package itself is installed.
Checks for specific browser providers, DOM environments (jsdom/happy-dom),
and coverage providers are skipped, as the custom configuration may handle
these or use alternative setups that the builder cannot predict.

(cherry picked from commit 98ffb68)

…runnerConfig

The Vitest unit test builder now correctly merges coverage thresholds and
watermarks from a user's Vitest configuration with CLI-provided options.
Previously, providing any CLI thresholds would completely replace the
configuration's thresholds. Now, partial CLI thresholds are merged, allowing
users to override specific metrics while keeping others from their config.

This change also ensures that the builder correctly reports failure when Vitest
coverage thresholds are not met by monitoring `process.exitCode`.

(cherry picked from commit 1f1b21d)

See associated pull request for more information.

…true' and 'false' string values in argument parsing

Handles booleans correctly

Closes #32361

(cherry picked from commit dbd81a7)

… and 'false' string values in argument parsing

Handles booleans correctly

Closes #32361

(cherry picked from commit 247855c)