Docs: Required outbound ports for Marketplace and Update Server

[CarlRodabaugh]

Summary

Add a reference doc that enumerates the outbound destinations (FQDNs/IPs) and ports a VergeOS system needs to reach the Marketplace and Update Server, so customers with restrictive egress firewalls can allow-list correctly.

Type

Reference

Suggested Content

• Audience: Network/security admins deploying VergeOS in environments with egress firewalls or proxies
• Prerequisites: Familiarity with VergeOS network concepts and firewall/ACL management on their edge
• Key sections:
  • Marketplace — destination FQDN(s), IP ranges if static, port (likely 443/tcp), protocol
  • Update Server — destination FQDN(s) for Verge.io Updates and Verge.io Trial/NFR, port, protocol
  • Whether traffic egresses from the management IP, node IPs, or both
  • Proxy support / behavior if a customer must route through one
  • Air-gap alternative pointer for environments that can't open egress at all
  • Quick allow-list table suitable for handing to a network team

Context

Requested via support interaction with Eric Moomjean @ NASA. Customers running VergeOS behind locked-down egress firewalls currently have to ask support to figure out what to open — a published reference would let them self-serve and would let the support chatbot answer the question directly instead of escalating.

Related context: case 12371 closed today after Paul confirmed the customer's path forward (open 443 to the world). The doc would have shortened that loop.