fix(trips): persist sessions across power cycles

[Tanchouteur]

This pull request implements a robust trip recovery feature, allowing users to resume or discard an interrupted driving session after an unexpected shutdown. It introduces new UI components for trip recovery, updates session state handling, and enhances the backend logic to manage trip checkpoints and recovery flows. Additionally, it improves the display of trip cost and session statuses in the UI.

Trip Recovery Feature:

• Added a new TripRecoveryDialog component that prompts the user to resume or start a new trip after an unexpected shutdown, displaying trip summary and a countdown timer (frontend/shared_pages/components/TripRecoveryDialog.qml, frontend/components/AppShell.qml, frontend/state/UiState.qml). [1][2][3]
• Implemented backend logic for checkpointing and recovery: the TripSessionManager now saves checkpoints, detects interrupted trips, and allows resuming or starting a new trip, publishing relevant session states and summaries (src/services/trip_session_manager.py).

Session State and UI Enhancements:

• Updated session state logic to include new states (SUSPENDED, RECOVERY_PENDING), and adjusted UI elements to reflect these, including status colors, labels, and button behaviors (frontend/styles/apex/pages/ApexDrivePage.qml). [1][2][3]
• Added display of estimated trip cost as a new metric in the drive page UI (frontend/styles/apex/pages/ApexDrivePage.qml).

Command Routing:

• Added support for a new UI command to start a new trip from the recovery dialog (src/bridge/ui_command_router.py).

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.