Analytics: Add journey and trip tracking events

[ksharma-xyz]

TL;DR

Refactored analytics tracking to include more detailed event properties and improved event handling across journey interactions.

What changed?

• Modified Analytics interface to handle event properties directly through AnalyticsEvent
• Added new analytics events for journey card expand/collapse with hasStarted property
• Updated DateTimeSelectEvent to use journeyOption instead of type
• Added analytics tracking for journey alerts, save trip actions, and date/time selections
• Created dedicated TimeTableAnalytics.kt file for journey card tracking functions
• Added analytics tracking when accessing the date/time selector

How to test?

1. Navigate through the time table screen and verify analytics events are fired:
   • Expand/collapse journey cards
   • Select different dates/times
   • Save trips
   • View journey alerts
2. Check Firebase Analytics dashboard to confirm events are logged with correct properties
3. Verify reverse trip functionality triggers appropriate analytics events

Why make this change?

To provide more comprehensive analytics data for user interactions, making it easier to track user behavior and improve the journey planning experience. The standardized event tracking will help better understand how users interact with time tables and journey planning features.

[ksharma-xyz]

• Release: Bump version codes for Android and iOS #469
• Analytics: Add stop selection and field click events #468
• Core: Rename AppPlatformType to DevicePlatformType and refactor AppInfo #466
• Analytics: Add app start event tracking #465
• Analytics: Add reset time click tracking #464
• Analytics: Add journey and trip tracking events #463 👈 (View in Graphite)
• Analytics: Add saved trip and theme selection events #462
• Analytics: Add screen view tracking #461
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.