fix(@angular/cli): skip CLI version check for migrate-only updates

When running `ng update @angular/cli --name=use-application-builder`,
the CLI would fetch and install the latest version (e.g., v20) as a
temporary CLI to perform the update, even though migrate-only mode
operates on the currently installed package version. This caused
incompatible packages to be installed (e.g., @angular/build@20 on
an Angular 18/19 project).

The fix skips the CLI version check when in migrate-only mode
(--name or --migrate-only), since migrations run against the
installed version and don't need a different CLI version.

Closes #30696

Author: maruthang

packages/angular/cli/src/commands/update/cli.ts

@@ -167,7 +167,9 @@ export default class UpdateCommandModule extends CommandModule<UpdateCommandArgs
 
     // Check if the current installed CLI version is older than the latest compatible version.
     // Skip when running `ng update` without a package name as this will not trigger an actual update.
-    if (!disableVersionCheck && options.packages?.length) {
+    // Also skip when using migrate-only mode (--name or --migrate-only) since migrations run
+    // against the currently installed package version, not a remote one.
+    if (!disableVersionCheck && options.packages?.length && !options.migrateOnly) {
       const cliVersionToInstall = await checkCLIVersion(
         options.packages,
         logger,