feat(sim): add capture-aware rf physics

[Komzpa]

Summary

• add a shared directed link-budget helper that combines distance, SRTM terrain from feat(sim): add map and terrain inputs #68, clutter from feat(sim): add land-cover clutter inputs #69, antenna gains, offsets, and reusable calibration features
• route packet RF visibility through that shared link-budget helper so terrain/clutter loss is applied in the RF physics layer, not in the input layer
• preserve feat(sim): add map and terrain inputs #68 terrain-backed absolute node altitudes for geometry while using separate antenna-height values for Hata/base path-loss terms
• add an opt-in empirical SNR-to-payload-loss model
• add a capture-aware overlap/collision model with CAD-detectable interference energy
• keep baseline simulator behavior disabled by default, with stats and focused tests for the new path

Stack

• split from draft rollup feat(sim): add Batumi radio physics for DCR #64
• stacked after feat(sim): add land-cover clutter inputs #69 / codex/split-clutter-osm
• intended review commit for this slice: 1f331e1

Validation

• /tmp/meshtasticator-pr68-venv/bin/python -m unittest tests.test_radio_loss tests.test_link_model tests.test_collision_model tests.test_lora_mesh_cli tests.test_node tests.test_terrain tests.test_clutter tests.test_osm_clutter tests.test_map_input
• /home/kom/.local/bin/ruff check loraMesh.py lib/config.py lib/common.py lib/map_input.py lib/node.py lib/packet.py lib/terrain.py lib/link_model.py lib/radio_loss.py lib/phy.py tests/test_radio_loss.py tests/test_link_model.py tests/test_collision_model.py tests/test_lora_mesh_cli.py tests/test_node.py tests/test_terrain.py tests/test_map_input.py
• git diff --check
• previously for this slice: compileall; full-suite baseline still has the unrelated test_discrete_sim_ten_nodes messageSeq mismatch from origin/master

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 359ba6dce7

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".