fix(companion): CLI NaN, APC on TX changes, tz-aware alarm, late ACKs, ping timeout and widths, TX limits

- set af / dutycycle / rxdelay reject nan.
- A TX power change from the app or CLI re-baselines APC.
- CMD_SET_RADIO_PARAMS stores repeat as 0/1.
- The alarm reschedules itself when the time zone changes.
- A late ACK for an earlier DM attempt marks it delivered.
- A new auto-advert interval counts from the last advert.
- Both UIs take the TX power range from radioctl, up to MAX_LORA_TX_POWER
  (30 dBm on the GAT562 30S).
- The ping timeout comes from the airtime; 3-byte path hash mode pings with
  4-byte trace hashes, and trace flags are right for width 4.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

examples/companion_radio/MyMesh.h

@@ -254,7 +254,7 @@ public:
     unsigned long sent_ms;
   };
   
-  uint32_t sendPing(const uint8_t* dest_pubkey, uint8_t hash_width = 1);
+  uint32_t sendPing(const uint8_t* dest_pubkey, uint8_t hash_width = 1, uint32_t* est_timeout = nullptr);
   void setPingCallback(PingCallback cb, void* arg);
   void clearPingResult(uint32_t tag);
   PingResult* getPingResult(uint32_t tag);
@@ -684,6 +684,8 @@ private:
   unsigned long _bot_last_ch_reply_ms;
   unsigned long _bot_last_room_reply_ms;
   unsigned long _next_auto_advert_ms;
+  unsigned long _last_auto_advert_ms = 0;
+  uint32_t _auto_advert_sec = UINT32_MAX;   // the interval _next_auto_advert_ms was set with (MAX: not yet)
 
   // Per-contact DM reply throttle: a small ring of the most recent recipients so
   // one chatty contact can't be spammed while a different sender is still served.