Fix testnet platform metrics ports

[vivekgsharma]

Summary

• render shifted platform service ports for testnet by default while keeping devnet/mainnet on existing ports
• make Prometheus scrape config use the same dashmate port variables instead of hardcoded base ports
• keep both base and shifted metrics ports open in the HPMN security group for mixed/transition states

Why

Recent testnet deploys rendered some HPMNs with base ports (9090, 9102, 29090) while older nodes still used shifted testnet ports (19090, 19102, 39090), which caused Prometheus target drift and alerts.

Validation

• ansible-playbook --syntax-check ... deploy.yml --tags full_deploy against testnet config
• rendered dashmate defaults locally for dash_network=testnet and dash_network=devnet
• git diff --check

Note: terraform fmt -check security_groups.tf still reports pre-existing whitespace-only formatting drift in that file outside this patch; I did not run broad formatting to avoid unrelated churn.

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 07be2aa5-46bb-4446-8097-4ee20a34d383

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch vivek/port_fix

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}