[mmc] Add commands to enforce direct path and power settings in repeater telemetry replies

[xyzw-io]

Motivation

Tangential to #1031: local telemetry meshes do not always need flood-routed replies. For same-site repeater polling, flood responses add avoidable public mesh traffic.

Changes

Adds opt-in repeater controls for admin telemetry replies:

set telem.reply.zerohop on
get telem.reply.zerohop

set telem.reply.power 10
get telem.reply.power

set telem.reply.power off

When telem.reply.zerohop is enabled, the repeater sends matching replies as direct zero-hop packets instead of using flood fallback. Zero-hop means the packet is transmitted once by the repeater and is not forwarded by other nodes.

telem.reply.power optionally overrides TX power for that reply only, then restores the normal node TX power afterward. off uses the normal configured tx value.

Defaults stay stock: zero-hop is off and reply power override is off. This PR is a workaround for local telemetry meshes, not a general fix for telemetry scaling.

[xyzw-io]

I can also scale back to only adding zero hop command for now. This will make PR a bit smaller.