[WIP] Fix time recording drift in Strava workouts

[Copilot]

• Run baseline tests to understand current state
• Investigate workout timing drift and identify fix
• Implement timing correction with minimal code changes
• Add regression test covering async timer delays
• Run targeted tests/analysis and validate functionality

Original prompt

The time recorded and uploaded to Strava during workouts is slowly drifting on each interval, causing the recorded workout to be shorter than the actual workout was. Please analyze this and make changes to this branch PR that will fix this. On a real workout I preformed to test this, the actual workout was 1:03 and we only recorded 59 minutes. When designing a test for this, you might have to purposfully add some random async delays to the test to simulate it running on actual hardware. The current tests all (falsely) test okay because the computer hardware they're running on is much more robust than Android tablets, and the test happens in just a few seconds instead of over minutes or hours which isn't enough time to accumulate a significant delay.

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.