…update

When `ng update` encounters packages using npm aliases (`npm:` protocol)
or packages that cannot be fetched from the registry (private registries,
JSR, AWS CodeArtifact), the entire update process would fail with a 404
error because `Promise.all()` rejects on any single fetch failure.

The fix:
1. Filters out `npm:` aliased packages early in `isPkgFromRegistry()` since
   the dependency key name differs from the actual package name
2. Catches individual fetch errors in the parallel metadata fetch, returning
   a partial result that the existing reduce logic already handles gracefully

Closes angular#28834