feat(mesh): Meshtastic region + shared-channel auto-provisioning (MeshCore parity)

Fresh Meshtastic radios ship region-UNSET (RF-silent) and on mismatched
channels, so nodes only ever saw themselves. Bring them to MeshCore parity
using the official Meshtastic admin API:

- Auto-provision LoRa region (set_config, AdminMessage field 34) from a new
  mesh-config `lora_region` (e.g. EU_868) when the radio's region differs.
- Auto-provision a shared primary channel (set_channel, field 33) with a
  PSK derived deterministically from channel_name, so every node converges on
  one mesh — the parity equivalent of MeshCore's named "archipelago" channel.
- Read current region/channel from want_config; only write when different
  (no reboot loop); cap attempts so a radio that won't persist can't loop.
- Active NodeInfo advert scaffolding + aggressive serial drain.

Verified on .116+.228: region+channel persist, discovery works (both see each
other as named reachable contacts), bidirectional RF + sending confirmed.
Receiving in the running driver is still under diagnosis (instrumentation added).

Also removes the unwanted `meshtastic` daemon app from the registry (it was
never meant to be a container — native driver provides system-level support):
deletes apps/meshtastic + catalog entries (app-catalog, neode-ui, releases) +
test refs. Meshtastic stays native, like MeshCore.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

tests/lifecycle/remote-lifecycle.sh

@@ -157,7 +157,6 @@ image_for() {
     indeedhub) echo "146.59.87.168:3000/lfg2025/indeedhub:1.0.0" ;;
     botfights) echo "146.59.87.168:3000/lfg2025/botfights:1.1.0" ;;
     gitea) echo "docker.io/gitea/gitea:1.23" ;;
-    meshtastic) echo "docker.io/meshtastic/meshtasticd:daily-alpine" ;;
     *) return 1 ;;
   esac
 }