…` when present

Add logic to automatically include `main.server.ts` in the `files` array of the tsconfig when present during schematic execution. This ensures backwards compatibility for applications generated prior to version 19.

Closes #30526

…g applications

The application schematic now invokes the module schematic with `typeSeparator` explicitly set to `undefined`. This ensures any legacy value from `angular.json` set by older versions of the Angular CLI is cleared during application generation and does not cause multiple files to be generated.

Closes #30497

See associated pull request for more information.

See associated pull request for more information.

…karma

When using the `karma` builder, the generated output JavaScript file was
unintentionally being marked as a module type script. This prevent the
output file from providing equivalent behavior to that of an actual build.
The `scripts` option outputs should be considered classic scripts to the
browser.

When using the `karma` builder with custom "scripts" option entries that
contain the `bundleName` suboption, the output files for these scripts
will now correctly be injected into the test index HTML content. Previously
only the default `scripts.js` output file would be used.

See associated pull request for more information.

…xclude

Fixes #30543

Avoids the error `resolved.coverage.exclude is not iterable` while running `ng test`.

The coverage reporters option is `reporter`, see https://vitest.dev/config/#coverage-reporter

They can be quite handy for analysis tools.

See https://github.com/vitest-dev/vitest/blob/93f3200e452874ed4e2d018718bbbde7ebd28590/test/coverage-test/test/configuration-options.test-d.ts#L152 for all the current valid options

This is a workaround for piscinajs/piscina#816

Closes #30549