Make peer propagation canonical in Dig2Go v52

[theysayheygreg]

Summary

• bump Tubes release authority from v51 to v52
• enable peer propagation, the legacy pull host, and dynamic enrollment in the canonical esp32_quinled_dig2go_tubes build
• remove the separate _p2p environment so v52 has one Dig2Go capability set
• include the local P! command, which constructs a self-targeted FleetUpdateOffer and enters the existing PR72 serving path
• keep propagation dormant until an explicit command or received baton starts a turn

Why v52

PR72 left ordinary and propagation-enabled Dig2Go binaries with the same v51 release identity. Equal-release admission means a propagation host cannot converge an ordinary v51 peer. A canonical v52 lets every v51 Dig2Go accept the same upgrade and every updated Dig2Go pass the baton.

Verification

• bash test/tubes_mesh/run.sh
• node --test tools/fleet-update-protocol-test.js
• pio run -e esp32_quinled_dig2go_tubes
• canonical Dig2Go artifact: 1,352,960 bytes, SHA-256 95917b296a7ca19e7cb104cd0c8b647618067e9cd4ade83f9b06cc1c582a9d31, parsed TUBEUP1 family 1 / variant 0 / Tubes 52
• pio run -e esp32-c3-athom_tubes
• pio run -e waveshare_s3_tubes_remote

The S3 carrier aggregate target still requires its normal pre-staged vault payloads; a direct carrier invocation without that staging correctly failed before compilation. No hardware was flashed. Easy Flash and its bundled artifacts are intentionally not updated in this PR pending maintainer discussion.