When using pnpm's `catalog:` protocol for dependency versions in
`package.json`, `ng update` would fail with "Package X was not found on
the registry" because the `catalog:` specifier is not a valid npm
package argument and cannot be resolved by the npm registry.

This change adds two fixes:
- `isPkgFromRegistry()` now recognizes `catalog:` as referencing
  registry packages instead of rejecting them
- `_getAllDependencies()` resolves `catalog:` specifiers to `^<version>`
  using the installed version from node_modules, providing a valid
  semver range for downstream processing

Fixes angular#30443