fix(@angular/cli): ensure update migrations are fully executed

With the move to refactor and centralize the update logic, the schematics wrapper context needs to be updated to create an exception for the new location of the update schematic.

Author: clydin

packages/angular/cli/models/schematic-engine-host.ts

@@ -32,9 +32,9 @@ function shouldWrapSchematic(schematicFile: string): boolean {
     }
   }
 
-  // Never wrap `@schematics/update` when executed directly
+  // Never wrap the internal update schematic when executed directly
   // It communicates with the update command via `global`
-  if (/[\/\\]node_modules[\/\\]@schematics[\/\\]update[\/\\]/.test(schematicFile)) {
+  if (/[\/\\]node_modules[\/\\]@angular[\/\\]cli[\/\\]/.test(schematicFile)) {
     return false;
   }
 

tests/legacy-cli/e2e/tests/update/update-8.ts

@@ -17,7 +17,10 @@ export default async function () {
 
     // Update Angular to 9
     await installPackage('@angular/cli@8');
-    await ng('update', '@angular/[email protected]', '@angular/[email protected]');
+    const { stdout } = await ng('update', '@angular/[email protected]', '@angular/[email protected]');
+    if (!stdout.includes('Executing migrations of package \'@angular/cli\'')) {
+      throw new Error('Update did not execute migrations. OUTPUT: \n' + stdout);
+    }
 
     // Update Angular to 10
     await ng('update', '@angular/cli@10', '@angular/core@10');