feat(angular): support Angular 22 (#31205)

Issue number: resolves #31204

---------

## What is the current behavior?

Currently, `@ionic/angular` on `major-9.0` supports Angular 18 through
21 and TypeScript 5.4 through 5.9. The library and
`@ionic/angular-server` don't build under Angular 22 / ng-packagr 22 /
TypeScript 6.0. TS 6.0 surfaces latent `tsconfig` problems (a `baseUrl`
the schematics build relied on, and `types` now defaulting to `[]`), and
Angular 22's `typeCheckHostBindings` rejects the `$event.target` host
bindings in `ion-tabs` and the multi-element value accessors. The
package also still lints with ESLint 8 and the legacy `.eslintrc.json`

## What is the new behavior?

This extends the supported Angular range to 18 through 22 and upgrades
TypeScript to v6.0. A new `ng22` test app is added, mirroring `ng21`
(zoneless), so the automated test matrix covers v18-22 end to end

The package's ESLint setup is migrated to the v9 flat config, which was
required by the upgrade to `angular-eslint@22`

Several shared test pages under `test/base/` were modernized to signals
(router-link, checkbox, the value-accessor display, and the lazy modal
example). Angular 22 defaults components without an explicit strategy to
`OnPush`, so plain-field state mutated from an Ionic lifecycle hook no
longer re-renders on its own in the test app

## Does this introduce a breaking change?

- [X] Yes
- [ ] No

Apps moving to Angular 22 inherit three Angular 22 requirements, all
documented in BREAKING.md: components without an explicit change
detection strategy default to `OnPush` (run `ng update` to migrate to
eager, or use a signal / `markForCheck()` for state set in lifecycle
hooks), TypeScript 6.0 or later is required, and the minimum Node.js
version rises to `^22.22.3 || ^24.15.0 || ^26.0.0`. Angular 18 through
21 are unaffected

## Other information

Angular 22's CLI hard-blocks Node below `^24.15.0` / `^22.22.3` /
`>=26`, so local `ng serve` / `ng test` of the `ng22` app needs a Node
version in that range

---------

## Current dev build (2026-06-10):
```
8.8.9-dev.11781098612.122c6758
```

Angular 22 test app:
https://ionic-framework-git-feat-ng22-ionic1.vercel.app/angular/
Docs PR: ionic-team/ionic-docs#4549
Docs Preview:
https://ionic-docs-git-feat-ng22-ionic1.vercel.app/docs/updating/9-0#angular

---------

Co-authored-by: Brandy Smith <brandyscarney@users.noreply.github.com>

Author: ShaneK

.github/workflows/build.yml

@@ -140,7 +140,7 @@ jobs:
     strategy:
       fail-fast: false
       matrix:
-        apps: [ng18, ng19, ng20, ng21]
+        apps: [ng18, ng19, ng20, ng21, ng22]
     needs: [build-angular, build-angular-server]
     runs-on: ubuntu-latest
     steps:

.github/workflows/stencil-nightly.yml

@@ -157,7 +157,7 @@ jobs:
     strategy:
       fail-fast: false
       matrix:
-        apps: [ng18, ng19, ng20, ng21]
+        apps: [ng18, ng19, ng20, ng21, ng22]
     needs: [build-angular, build-angular-server]
     runs-on: ubuntu-latest
     steps:

BREAKING.md

@@ -175,9 +175,17 @@ Angular forbids `provideZoneChangeDetection()` inside an NgModule's `providers`
 import 'zone.js';
 ```
 
+**OnPush by Default on Angular 22**
+
+Angular 22 changes the default change detection strategy to `OnPush` for components that don't declare one. Combined with the zoneless default above, any component state that you mutate as a plain field from an Ionic lifecycle hook (`ionViewWillEnter`, etc.) no longer re-renders on its own. Run `ng update`, which migrates existing components to eager change detection and preserves the previous behavior, or use a signal (or `ChangeDetectorRef.markForCheck()`) for state set in those hooks. Ionic's own Angular components already declare `OnPush` explicitly and are unaffected. Angular 18 through 21 keep the eager default, so they require no change.
+
 **TypeScript**
 
-Ionic 9 supports TypeScript 5.4 or later, matching the minimum for Angular 18. Angular 21 requires TypeScript 5.9 or later per Angular's own requirements.
+Ionic 9 supports TypeScript 5.4 or later, matching the minimum for Angular 18. Angular 21 requires TypeScript 5.9 or later, and Angular 22 requires TypeScript 6.0 or later, per Angular's own requirements.
+
+**Node.js**
+
+Angular 22 raises the minimum Node.js version to `^22.22.3 || ^24.15.0 || ^26.0.0`. Angular 18 through 21 are unaffected.
 
 **Module Resolution**