Companion firmware (MeshCore commit 4a869163, 2025-12-30) replaces the
CLI frame timestamp with the companion node's RTC for TXT_TYPE_CLI_DATA,
so "clock sync" sets the repeater clock to the node RTC. Nodes with a
wrong RTC push repeater clocks years into the future; firmware cannot
set the clock backwards without clkreboot.
- RepeaterCommandService: translate "clock sync" to "time <phone epoch>"
before sending, matching official meshcore-cli behavior
- repeater login dialog: send "time <epoch>" for auto clock sync after
login (this path bypasses RepeaterCommandService)
- add unit tests for the command translation
Ref: https://github.com/zjs81/meshcore-open/issues/464