Add support for Vitest VSCode Plugin and similar

### Command

test

### Description

As Angular does not provide a Vitest plugin, it can't expose a `vitest.config.ts` file to 3rd party tools such as IDEs.

This means that as of today, it is impossible to use Vitest VSCode Plugin, nor WallabyJS, nor WebStorm integration etc... unless users switch to Analog plugin https://analogjs.org/docs/features/testing/vitest

### Describe the solution you'd like

_No response_

### Describe alternatives you've considered

_No response_

Start with the `test` command and investigate how Angular currently exposes Vitest configuration to external tools. Reproduce the limitation with the Vitest VSCode Plugin, then compare the behavior with the Analog plugin mentioned in the issue. Done means the plugin and similar integrations can discover the Angular project's Vitest configuration without switching plugins.

Written by the indexing model from the issue text.