Add terrain and traffic alerts/warnings, track log, distance rings

[h2orules]

This pull request introduces a comprehensive path-prediction, conflict, and terrain alerting engine to the app, along with related architectural and documentation updates. It adds new stores and services for path prediction, track logging, and terrain scanning, and updates the UI overlays and documentation to reflect these features. The change also expands test coverage and clarifies the app’s advisory-only status regarding conflict information.

Major feature: Path prediction, conflict, and terrain alerting engine

• Architecture & State Management

  • Added a new path store to Zustand, updated the store count in both documentation and code structure references, and included new shared types for path prediction. [1] [2]
  • Introduced new geo functions and services for prediction, hold entry, conflicts, terrain scanning, TCAS tables, range rings, track logging, and terrain elevation.

• Path Prediction & Alerting Engine

  • Implemented a per-poll path prediction engine (usePathEngine.ts) that predicts aircraft positions, detects hold entries, evaluates traffic conflicts (TCAS TA/RA, radar tiers), and performs terrain scanning with MVA and DEM data. Results are stored in the new path store and drive overlays and alert UI.
  • Ensured terrain alerting loads MVA sectors and prefetches nearby DEM tiles independently of display toggles, with efficient cache and async fetch behavior.
  • Added a real-time, imperative RangeRingsLayer overlay that tracks the selected aircraft’s interpolated position every frame, alongside overlays for track logs, hold entries, and predicted paths. [1] [2]

• UI & Documentation Updates

  • Updated the documentation to describe the new overlays, their order, and how they interact with aircraft selection and alerting. Clarified that overlays and data blocks now render traffic/terrain alert chrome.
  • Clarified in the Not For Navigation disclaimer that while conflict indicators are shown, separation and deconfliction are not guaranteed.
  • Added CSS documentation for label separation logic in conflict pairs.

• Configuration & Testing

  • Documented new configuration groups for the path-prediction engine (e.g., TRACKLOG_*, PREDICT_*, HOLD_ENTRY_*, CONFLICT_*, RADAR_*, TERRAIN_*, RING_ZOOM_BUCKETS) and updated test coverage expectations for the new logic.
  • Increased the documented test count to reflect new unit tests for the path-prediction and alerting logic.

• CIFP Parser Version Bump

  • Bumped the CIFP parser version from 21 to 23 to invalidate stale/buggy parses after parser logic changes.