fix(@angular/cli): expand package groups for newly added peer dependencies in update schematic

Previously, the package group stabilization loop ran completely before the peer dependencies resolution loop. If a peer dependency was newly added during the peer dependencies loop (e.g., @angular/core), its corresponding package group members (e.g., @angular/router) were never expanded, leaving them at outdated versions.

Now, wrap the package group and peer dependencies stabilization logic in a single outer loop so that newly added peer dependencies are also stabilized and their package groups are correctly expanded.

(cherry picked from commit 4b1b899)

Author: alan-agius4

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

@@ -882,14 +882,16 @@ export default function (options: UpdateSchema): Rule {
     let lastPackagesSize;
     do {
       lastPackagesSize = packages.size;
-      npmPackageJsonMap.forEach((npmPackageJson) => {
-        _addPackageGroup(tree, packages, npmDeps, npmPackageJson, logger);
-      });
-    } while (packages.size > lastPackagesSize);
 
-    // This is done in seperate loop to ensure that package groups are added before peer dependencies.
-    do {
-      lastPackagesSize = packages.size;
+      let lastGroupSize;
+      do {
+        lastGroupSize = packages.size;
+        npmPackageJsonMap.forEach((npmPackageJson) => {
+          _addPackageGroup(tree, packages, npmDeps, npmPackageJson, logger);
+        });
+      } while (packages.size > lastGroupSize);
+
+      // This is done in seperate loop to ensure that package groups are added before peer dependencies.
       npmPackageJsonMap.forEach((npmPackageJson) => {
         _addPeerDependencies(tree, packages, npmDeps, npmPackageJson, npmPackageJsonMap, logger);
       });