refactor: derive Gateway routes from node mode with listener-based hostnames

[bdchatham]

Summary

Replace baseDomain/hostnames CRD fields with mode-derived route generation. The Gateway owns the protocol topology — deployments just attach to it.

What Changed

CRD simplification — GatewayRouteConfig reduced to just annotations. No more baseDomain or hostnames fields. Gateway config just needs to exist (non-nil) to enable routing.

EVM merge — evm-rpc and evm-ws consolidated into single evm listener. Envoy handles WebSocket upgrade natively. Matches industry standard (Alchemy, Infura, QuickNode all use one URL for HTTP + WS).

Mode-derived routes — listeners determined by NodePortsForMode():

• Full/Archive → 4 routes: evm, rpc, rest, grpc
• Validator → 0 routes (no public traffic)

Hostname pattern — {deployment}.{protocol}.{domain}:

pacific-1.evm.prod.platform.sei.io   → :8545
pacific-1.rpc.prod.platform.sei.io   → :26657
pacific-1.rest.prod.platform.sei.io  → :1317
pacific-1.grpc.prod.platform.sei.io  → :9090

New platform env var — SEI_GATEWAY_DOMAIN (required) for hostname construction.

Why

• Deployment names (rpc) were conflating with protocol names in subdomains
• Multiple deployments of the same type would collide on hostnames
• EVM HTTP/WS split was non-standard (no EVM provider does this)
• Protocol routing is a Gateway concern, not a per-deployment concern

See design rationale: SeiKnowledgeBase/memories/node-configuration/networking-design-rationale.md

Test plan

• make test passes
• make lint passes (0 issues)
• make manifests generate produces clean CRDs
• Verify full mode generates 4 HTTPRoutes with correct hostnames
• Verify validator mode generates 0 HTTPRoutes
• Verify EVM route covers both HTTP and WebSocket (single hostname)

🤖 Generated with Claude Code