Revert "RAK4631 analogue user button on input 31"

Merge Dev

Revert "RAK4631 analogue user button on input 31"

Merge Dev

…alidation

- Issue meshcore-dev#3: Replace all strcpy/sprintf with strncpy/snprintf to prevent buffer overflows
  * Fixed CommonCLI.cpp: All command responses now use bounded string operations
  * Fixed RegionMap.cpp: Safe string copying for wildcard name
  * Removed password echoing (security issue)

- Issue meshcore-dev#7: Improve Packet::readFrom() validation
  * Add bounds checking before all memory operations
  * Validate minimum packet size upfront
  * Check transport codes fit in buffer before copying
  * Verify path_len and payload_len before memcpy
  * Prevent buffer overruns from malformed packets

Default LNA enabled=true and fix the sleep order

[codex] improve photon repeater GPS behavior

… placeholders

Three related improvements grouped because they share the same console.py
file and would require interactive hunk-staging to split:

1) `get all` virtual command (console-side intercept):
   - Same output as the --get-all CLI flag, but available inside the
     interactive shell as `get all`.
   - Added "all" to GET_PROPS so tab completion offers it.
   - Added intercept_with_serial() helper for commands that need the
     serial port (vs the existing intercept() for pure client-side
     commands like help/exit).
   - Added 3 more entries to GET_ALL_COMMANDS that were missing:
     `board` (hardware manufacturer/model), `clock` (RTC time, useful
     for sync verification), and `get bridge.type` (legacy bridge
     compilation status).

2) Event-driven send_and_collect (console-side performance):
   - Was: fixed `settle` sleep + drain loop. Each command paid ~500ms
     regardless of actual reply time. `--get-all` took ~25s.
   - Now: poll for the firmware's `  -> <reply>\\n` marker pattern;
     return as soon as the reply is complete. Typical reply: 30-80ms.
   - `settle` parameter now means "no-reply fallback timeout" (default
     0.1s) instead of fixed initial wait. Reply-producing commands
     extend the deadline by 200ms once the marker is seen, so slow
     replies don't get truncated.
   - `--get-all` now takes ~2-4s; single `get foo` ~30-80ms.
   - Function signature and default value preserved -- all existing
     callers (one-shot, batch, interactive) work without changes.

3) {client_id} / {pubkey} placeholders in mqtt.topic_prefix and
   mqtt.subscribe (firmware change):
   - New expandPlaceholders() helper in MqttBridge. Substitutes
     {client_id} (resolved client id, possibly auto-derived from
     pubkey) and {pubkey} (first 8 hex chars of this device's pubkey).
     Unknown placeholders pass through literally.
   - Applied at connect time so changes to mqtt.client_id automatically
     re-resolve the topic_prefix on next applyMqttConfig() cycle.
   - The empty default for mqtt.topic_prefix is now conceptually
     "meshcore/{client_id}" -- runs through the same expansion path
     instead of being a separate hard-coded snprintf.
   - Console help (`help mqtt`) and BLANK_DEFAULT_DESCRIPTIONS updated
     to mention placeholders, with examples.

Footprint impact for meshcore-dev#3 (firmware): +176 bytes RAM, +928 bytes flash.
Total stack at heltec_v4_repeater_mqtt: 3.6% RAM, 20.4% flash.

… constants (meshcore-dev#3), make irqDioNum configurable (meshcore-dev#4)