PR Checklist

Current behavior: the Angular canary compatibility harness resolved @angular/core@next first and then reused that exact framework version for most @angular/* packages. When Angular framework next advanced to 22.1.0-next.0 but CLI-owned packages such as @angular/build remained at 22.0.0, the canary attempted to read npm metadata for a package version that does not exist.

Closes: N/A

What is the new behavior?

• Treat Angular framework packages as an explicit release-train allowlist for exact version reuse.
• Resolve CLI-owned packages, including @angular/build and @angular/cli, from their own npm dist-tags.
• Add focused tests that model the framework/CLI next skew and ensure the resolver never asks for @angular/build@22.1.0-next.0.
• Document why canary toolchains resolve framework and CLI packages separately.

Does this PR introduce a breaking change?

• Yes
• No

Other information

Verified with:

• pnpm --filter @limitless-angular/angular-compat test
• pnpm turbo run test --filter=@limitless-angular/angular-compat
• pnpm --filter @limitless-angular/angular-compat run compat:assert
• pnpm --filter @limitless-angular/angular-compat run --silent compat:matrix --canary
• Live resolver smoke check for angular-next, which now resolves Angular 22.1.0-next.0, @angular/build 22.0.0, and @angular/cli 22.0.0.

[Optional] What gif best describes this PR or how it makes you feel?