Telemetry collection could start before system clock is set

[kezarjg]

Telemetry collection can start before the system clock is properly initialized, leading to incorrect UTC timestamps in the telemetry data sent to A Better Routeplanner (ABRP) and other services. This can cause misalignment in telemetry data and inaccurate reporting of events.

[kezarjg]

Proposed Solution:
Time Validation Check:
Before starting telemetry collection or sending telemetry data, check that the system clock has been properly set.
Use a minimum valid timestamp (e.g., January 1, 2000) to verify the clock has been set correctly.