fix(@angular/cli): do not sort migrations of the same version alphabetically

When executing update migrations, schematics targeting the same version were previously sorted alphabetically by name. This change removes the alphabetical sorting fallback, allowing migrations targeting the same version to preserve their original declaration/discovery order.

Author: alan-agius4

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

@@ -153,9 +153,7 @@ export async function executeMigrations(
   if (requiredMigrations.length) {
     logger.info(colors.cyan(`** Executing migrations of package '${packageName}' **\n`));
 
-    requiredMigrations.sort(
-      (a, b) => semver.compare(a.version, b.version) || a.name.localeCompare(b.name),
-    );
+    requiredMigrations.sort(compareMigrations);
 
     const result = await executePackageMigrations(
       workflow,
@@ -174,9 +172,7 @@ export async function executeMigrations(
   if (optionalMigrations.length) {
     logger.info(colors.magenta(`** Optional migrations of package '${packageName}' **\n`));
 
-    optionalMigrations.sort(
-      (a, b) => semver.compare(a.version, b.version) || a.name.localeCompare(b.name),
-    );
+    optionalMigrations.sort(compareMigrations);
 
     const migrationsToRun = await getOptionalMigrationsToRun(
       logger,
@@ -372,3 +368,10 @@ function getMigrationTitleAndDescription(migration: MigrationSchematicDescriptio
       : undefined,
   };
 }
+
+function compareMigrations(
+  a: MigrationSchematicDescriptionWithVersion,
+  b: MigrationSchematicDescriptionWithVersion,
+): number {
+  return semver.compare(a.version, b.version);
+}