Fix bare-metal Kura regions: use shared regional gateway

Kura instances on bare-metal (host-network) regions now actually serve traffic. Previously, accounts marked for a dedicated gateway got a per-account host-network controller that collided with the platform’s shared controller for ports 80/443, leaving the dedicated gateway unschedulable (“no free ports”) and silently breaking the account’s Kura deployment even though the shared platform gateway was healthy. Dedicated accounts on bare-metal regions now fall back to the shared regional ingress class, so they begin serving as soon as they roll out (existing instances automatically after a Destroy → Deploy). LoadBalancer regions and non-dedicated accounts are unchanged.