Even with an RTC, nodes lose accurate time over the long run. This adds a one-tap Set time action to the remote Administration section so a user can push an accurate clock to a drifted node without being on-site or dropping to the CLI.

Resolves #5789

🌟 New Features

• "Set time" remote admin action. New AdminRoute.SET_TIME entry (clock icon + set_time string) at the top of the Administration screen. Tapping it shows the standard confirmation dialog and, on confirm, sends the phone's current time to the selected node.
• Behavior matches the existing admin actions: the flow runs the SESSIONKEY_CONFIG preflight first (which seeds the remote session passkey), then sends the command; completion rides the routing ACK exactly like reboot/shutdown.

🛠️ Refactoring & Architecture

• Added setTime(destNum, packetId) to the AdminController interface and AdminControllerImpl, which sends AdminMessage(set_time_only = <current epoch seconds>) via the existing CommandSender. The timestamp is resolved at send time (using the shared nowSeconds accessor) so it is as fresh as possible when it leaves the phone. This mirrors the SDK AdminApi boundary and the Python CLI's Node.setTime.
• Added AdminActionsUseCase.setTime(destNum) and wired the AdminRoute.SET_TIME branch in RadioConfigViewModel.sendAdminRequest.
• Fire-and-forget by design: set_time_only has no admin response (consistent with the local-node time-set already sent during the connection handshake).

🧹 Chores

• Added the set_time string resource and re-ran scripts/sort-strings.py (regenerates strings-index.txt).
• Added the setTime no-op override to the FakeRadioController test double.

Testing Performed

• Added setTimeSendsAdminMessageWithCurrentEpochSeconds to RadioControllerImplTest, which captures the sent AdminMessage and asserts set_time_only is populated with a plausible recent epoch timestamp.
• Ran the full baseline locally — all green: spotlessApply spotlessCheck detekt assembleDebug test allTests kmpSmokeCompile.