Fix LetsMesh MQTT Status Parity: Accurate Startup Metadata, Radio Format Alignment, and Secure Owner Claims

[yellowcooln]

Summary

This PR improves meshcore-ha parity with meshcoretomqtt and meshcore-packet-capture for LetsMesh compatibility and UI consistency.

---

What Was Fixed

• Fixed logging format error in the connect validation path.

• Fixed MQTT origin name drift by:

  • updating from live SELF_INFO
  • republishing retained online status on rename
  • seeding startup origin from connect-time SELF_INFO to prevent reboot regressions

• Fixed radio format in status payload for LetsMesh grouping:

  • Before: 910.525/62.5/SF7/CR5
  • After: packet-capture schema 910.525,62.5,7,5

• Fixed startup unknown metadata by priming the status cache before the first online publish:

  • model
  • firmware_version
  • radio

• Added security parity for optional JWT identity claims:

  • owner and email are now included only when use_tls=true and tls_verify=true

---

Documentation

• Updated MQTT documentation to clearly state the TLS requirements for owner and email JWT claims.

---

User Impact

• LetsMesh overview remains consistent after node rename and Home Assistant reboot.
• LetsMesh modulation/category grouping now matches other uploaders.
• Status payload no longer starts as unknown when metadata is available.
• owner and email claims are no longer sent over insecure or unverified broker connections.

---

Before / After Screenshots

Before YC-Observer was showing up in the 910.525/62.5/SF7/CR5 section.

Now its showing up in the correct section 910.525 MHz / SF7 / BW62.5