fix(misc): stop generators from accepting targets on removed executors - #37475

`nx g @nx/vite:configuration` converted projects that still had targets on removed
executors such as `@nx/webpack:webpack`, `@nx/rollup:rollup` and `@nx/vite:build`.
A leftover target replaces the inferred target of the same name, so the converted
project kept running the removed executor.

The generator now stops before changing anything and asks to convert those
targets first. The supported build list drops `@nx/rollup:rollup`, which it now
refuses, and `@nx/js:babel`, which never existed. The config lookup stops
matching `@nrwl/vite:build` targets, and the examples page lists the executors
the generator checks.

`nx g @nx/rspack:configuration` treated targets on removed executors such as
`@nx/webpack:webpack` and `@nx/vite:build` as supported, and converted the
project around them. It refused targets on the removed `@nx/rspack` executors
only in some cases. A leftover target replaces the inferred target of the same
name, so the converted project kept running a removed executor.

The generator now stops before changing anything when a target uses one of those
executors, and asks to convert it first. The `buildTarget` and `serveTarget`
descriptions stop mentioning the Vite executors, and framework detection reads
`jestConfig` from any test target.

…xecutor

The lint-checks generator edited lint targets on `@nx/eslint:lint` that listed
`lintFilePatterns`. It added the plugin's JSON files to the patterns and made
lint depend on build. That executor no longer exists, so the code could only
touch targets that can't run. Inferred lint targets never got these changes.

The lint project and init generators still looked for targets on the removed
`@nx/eslint:lint` and `@nx/linter:eslint` executors. The `getEslintTargets`
helper and the executor's `Schema` type in `@nx/eslint/internal` had no
remaining users.

The Storybook utilities and the React stories and Storybook framework helpers
still matched targets on removed executors, including `@nx/next:build`,
`@nx/rollup:rollup`, `@nx/expo:build` and the `@nx/storybook` executors. The
Cypress build target error kept a framework hint that never matched, because it
received the target string split into characters. The vitest `testTarget`
description names the inferred target.

The rollup and vite library examples described `@nx/rollup:rollup` and
`@nx/vite:build` targets, and set the rollup compiler in project.json. They now
describe the targets the plugins infer, and set the compiler through `withNx` in
`rollup.config.cjs`. The `@nx/js:node` example linked `@nx/webpack:webpack` for
`buildLibsFromSource`, and now names the `NxAppWebpackPlugin` option.

The component testing example passed `--build-target:some-react-app:build`,
which the CLI parses as an unknown flag. A note pointed to Storybook testing
through Cypress, which Nx removed in 2024. The library examples said rollup
builds default to the `tsc` compiler, while the generated config uses `swc`.

…sal tests

The refusal tests for React component testing, Vite and Rspack matched
only the start of each error, so dropping the
`nx g @nx/workspace:infer-targets` suggestion kept them green. The
expected messages include the suggestion with each project's name.