Rewrite: SignalWire Firewall Config adjustment/removal

[Manny-r31]

Current state

• Source file: /signalwire-fern-config/fern/products/platform/pages/platform/core/allowing-signalwire-ips-through-your-firewall.mdx
• Live URL: https://signalwire.com/docs/platform/allow-signalwire-ips-through-your-firewall
• Page type (Fern): reference
• Approx. length: 22 lines (~70 words of body content)
• Effort estimate: M

What's there today

• Single-paragraph intro stating SignalWire does not publish static IPs
• Three bash command examples (one each for sip.signalwire.com, relay.signalwire.com, firewall.signalwire.com) using dig, egrep, awk, and iptables
• A Warning component cautioning against hardcoded IPs and noting that media originates from non-deterministic locations
• Minimal context about audience (implicitly assumes Linux firewall admins)
• Front matter missing description and max-toc-depth: 3 fields

Reviewer's concern

"This page should be a support template and a footnote on another doc at most. It does not require its own page."

Problems

• Insufficient content for standalone page: At ~70 words of body text (plus code snippets), the page is too narrow to justify its own navigation entry in the Core section. It reads as a FAQ answer or support KB snippet, not a guide or reference topic.
• Missing context: No explanation of when a user would need this, which customers/use cases apply, or what the three domains are used for (SIP signaling, relay, firewall management).
• Unclear parent relationship: No cross-reference to API credentials, setup guides, or network security topics that would establish context.

Proposed rewrite

Consolidate content into API Credentials or Setup guide or move content into support knowledgebase: Move the domain-resolution guidance to a note or callout in a broader setup guide. This could also live in Zoho as a reference for support to utilize or provide to customers via the knowledge base we have set up already.