chore: update Angular to 22.0.0-rc.0

[Copilot]

Upgrades the project from Angular 21.x to Angular 22.0.0-rc.0 using ng update, including all automated migration schematics.

Changes

• Angular packages — all @angular/* and @angular-devkit/* packages bumped to 22.0.0-rc.0
• Build tooling — ng-packagr → 22.0.0-next.4, TypeScript → 6.0.3
• Node.js requirement — Angular 22 CLI requires Node.js ≥ v22.22.0 (up from v18/v20)
• Auto-migrations applied by ng update:
  • provideHttpClient() calls updated with withXhr() where HttpXhrBackend is used
  • provideClientHydration() updated with withNoIncrementalHydration() opt-out to retain pre-v22 behavior
  • Optional chaining expressions in templates wrapped with $safeNavigationMigration()
  • Extended diagnostics nullishCoalescingNotNullable & optionalChainNotNullable disabled in all tsconfig files
  • Test spec files updated (~370 files touched by migration schematics)

[damyanpetev]

@copilot the install seems to be failing for peer deps of angular-eslint to angular packages
https://github.com/IgniteUI/igniteui-angular/actions/runs/25916675579/job/76184965619?pr=17276
Add an dependency override for those package deps with the 22 versions

[Copilot]

@copilot the install seems to be failing for peer deps of angular-eslint to angular packages
https://github.com/IgniteUI/igniteui-angular/actions/runs/25916675579/job/76184965619?pr=17276
Add an dep...

Fixed in c0f0c6d. Added npm overrides entries for @angular-eslint/builder and @angular-eslint/schematics (the two packages with @angular/cli >= 21.0.0 < 22.0.0 peer deps) using "$@angular/cli" to reference the root-level Angular CLI version. Also updated the existing igniteui-angular-charts and igniteui-angular-core overrides from ^21.0.0 to ^22.0.0-rc.0. Verified npm ci completes cleanly with no ERESOLVE errors.

[damyanpetev]

@copilot The CI build fails with the following:

> igniteui-dev-demos@0.0.0 build:lib
> ng build igniteui-angular --configuration production && npm run build:styles

Building Angular Package

------------------------------------------------------------------------------
Building entry point 'igniteui-angular/animations'
------------------------------------------------------------------------------
- Compiling with Angular sources in partial compilation mode.
✖ Compiling with Angular sources in partial compilation mode.
error TS5101: Option 'baseUrl' is deprecated and will stop functioning in TypeScript 7.0. Specify compilerOption '"ignoreDeprecations": "6.0"' to silence this error.
  Visit https://aka.ms/ts6 for migration information.

Per the link:

In old versions of TypeScript, baseUrl was required in order to use paths. This is no longer the case, and in many projects you can simply remove baseUrl (especially if it's .).
Otherwise, prepend the baseUrl value to each paths entry.

Check if its possible that the baseUrl can be removed and verify the build passes

[Copilot]

@copilot The CI build fails with the following:

> igniteui-dev-demos@0.0.0 build:lib

...

Fixed in 4a57cf2. Removed baseUrl: "./" from both tsconfig.json and projects/igniteui-angular-i18n/tsconfig.build.json. Per the TypeScript 6.0 migration guide, since baseUrl was "./" in both files, the fix is to remove baseUrl and prepend ./ to the non-relative path values in tsconfig.json (e.g., "projects/igniteui-angular/src/public_api.ts" → "./projects/igniteui-angular/src/public_api.ts"). The i18n tsconfig paths already used explicit ../../ relative paths so only baseUrl removal was needed there. Verified tsc -p tsconfig.json no longer produces any TS5101 or TS5090 errors.