debug(local-docker): temporarily drop 80/443 to test privileged-port hypothesis

v0.3.6 with the four-port config (6443/80/443/8944) still ships
NetworkSettings.Ports={} on ubuntu-latest, even though the
HostIP fix landed in y-cluster#15. y-cluster's own e2e on the
same runner works with two high-port forwards (36443:6443 +
38080:8080). Differential is privileged ports 80/443.

Drop them temporarily so the next CI run can tell us whether
removing the privileged forwards unblocks the apiserver readyz
probe. Restore once root cause is identified.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: solsson

cluster-configs/local-docker/y-cluster-provision.yaml

@@ -13,9 +13,12 @@ context: local
 name: local
 
 portForwards:
+# 80 and 443 temporarily dropped while investigating the
+# silent-drop on ubuntu-latest. With all four forwards (including
+# the privileged ports) Docker Engine 28 publishes nothing
+# (NetworkSettings.Ports={}), even with v0.3.6's HostIP fix.
+# Restore once the root cause is identified.
 - {host: "6443", guest: "6443"}
-- {host: "80",   guest: "80"}
-- {host: "443",  guest: "443"}
 - {host: "8944", guest: "8944"}
 
 # Mirror in-cluster registry hostnames at the magic ClusterIPs that