chore(deps): bump ng-packagr to 22.0.0 in multiple-apps example

[just-jeb]

PR Checklist

• Tests for the changes have been added (for bug fixes / features) — covered by the existing jest: multi-project library integration test
• Docs have been added / updated (for bug fixes / features) — N/A

PR Type

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[x] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe: dependency bump in a test-fixture example

What is the current behavior?

examples/jest/multiple-apps still pins ng-packagr at 21.2.3 while the rest of its toolchain is on the Angular 22.0.0-rc.2 line — a full major behind. This is the v22 counterpart of Renovate #2269 (which targeted master and was closed; the bump belongs on release/v22).

Issue Number: N/A (replaces #2269)

What is the new behavior?

ng-packagr bumped to 22.0.0 (the only published 22.x; no RC line). Its peer typescript >=6.0 <6.1 is satisfied by the example's 6.0.3. Aligns the major with the rest of the v22 toolchain and reduces the current version skew.

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Test-fixture dependency only — not a published package.

Other information

Targets release/v22. ci:full label applied so the jest: multi-project library integration test (which builds this example's library via ng-packagr) actually runs — an example-only change can otherwise be skipped by Turbo's affected-package filter.