fix(@angular/cli): keep relative migration paths during update analysis

The original update analysis would prepend the package name to all migration collection files. This was required at the time to ensure the migration collection files would be found. The existing update logic, however, no longer requires this change but the change previously had no negative effects as both the relative and module specifier methods would successfully resolve the migrations. But with the conversion to ESM-based packages that use the package.json `exports` field, deep imports into a package are no longer possible unless the migration collection files are explicitly exported. Relative migration collection paths are now preferred since they are based off of the location of the package's `package.json` and do not require additional `exports` field entries. The original update analysis logic, unfortunately, prevent the relative paths from working as intended. Since this original logic is no longer required by the update process, it has been removed allowing the relative paths to be kept and used directly.

Author: clydin

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

@@ -325,13 +325,9 @@ function _performUpdate(
         return;
       }
 
-      const collection =
-        (target.updateMetadata.migrations.match(/^[./]/) ? name + '/' : '') +
-        target.updateMetadata.migrations;
-
       externalMigrations.push({
         package: name,
-        collection,
+        collection: target.updateMetadata.migrations,
         from: installed.version,
         to: target.version,
       });