chore: upgrade Angular to v22.1.2 across all Angular projects

[Copilot]

Summary

Upgrades the full Angular stack to the latest stable version (v22.1.2) in all 5 Angular projects in the repository. Uses ng update schematics (run in an isolated environment) to apply the correct migrations for breaking changes, then applies those same migrations consistently across all projects.

Projects Updated

Project	From	To
examples/fdc3-chart-and-grid/js-datagrid	v21.1.x (with v20 inconsistencies)	v22.1.2
examples/js-chart-and-grid-messagerouter/js-datagrid	v21.1.x (with v20 inconsistencies)	v22.1.2
examples/fdc3-trade-simulator/js-trader-app	v21.1.x (with v20 inconsistencies)	v22.1.2
examples/fdc3-trade-simulator/js-order-book	v21.1.x (with v20 inconsistencies)	v22.1.2
prototypes/process-explorer/oss-frontend	v20.3.x	v22.1.2

Changes Per Project

package.json

• All @angular/* packages → 22.1.2
• @angular/cli + @angular/build → 22.1.4
• typescript → 6.0.3 (required by Angular 22: >=6.0 <6.1)
• zone.js → ~0.16.0 (Angular 22 supports ~0.15.0 || ~0.16.0)
• Added istanbul-lib-instrument ^6.0.3 (added by ng update @angular/cli migration for Karma coverage)

Source files (ng update @angular/core schematic)

• Added changeDetection: ChangeDetectionStrategy.Eager to all 16 @Component decorators across all projects. ChangeDetectionStrategy.Eager is the new Angular 22 name for the default change detection strategy (value 1, aliased to Default for backwards compatibility).

tsconfig.app.json + tsconfig.spec.json (ng update @angular/core schematic)

• Added angularCompilerOptions.extendedDiagnostics.checks to suppress nullishCoalescingNotNullable and optionalChainNotNullable diagnostics, which became errors in Angular 22's stricter template checking defaults.

How schematics were applied

Because this repository uses npm workspaces, ng update cannot be run directly from sub-project directories (it reads the workspace root's package.json). Instead:

1. An isolated copy of one project was created in /tmp, reset to v21, and ng update was run there to discover all migration changes
2. The same migrations were then applied consistently across all 5 projects

Optional migrations available (not applied)

The ng update @angular/cli schematics also offer two optional migrations that were intentionally skipped:

• Migrate Karma to Vitest – ng update @angular/cli --name migrate-karma-to-vitest
• Migrate to new application builder – ng update @angular/cli --name use-application-builder