getClockMonotonic added monotonicClockOffset on top of the uptime. That
offset is indeterminate until the first setClock call and jumps when it is
latched, so every Countdown and Stopwatch armed before that point either
expires immediately or measures against garbage.
The monotonicity came from the uptime alone, the offset only made the value
look epoch based. The Linux and host implementations return
CLOCK_MONOTONIC_RAW with no offset, so this also makes the OSALs agree.
All users take differences only: Countdown, Stopwatch and PeriodicHelper.
Also drops the Clock statics monotonicClockInitialized and
monotonicClockOffset, which were declared but never defined or used.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>