disable access to control routes via 192.168.127.1

Using the podman machine, containers can access forwarder controls via `curl -s 192.168.127.1/...`. This behavior should probably be disabled or gated in some way.

It has security implications if end users decide to use podman to host containerized applications on Mac for example, which is something that absolutely happens with Docker for Desktop on Mac.

Start by reproducing the container access described with a Podman machine and curl against 192.168.127.1, then trace how the forwarder control routes are exposed. Done means containers cannot reach those controls, or access is explicitly gated, while the intended control access remains available.

Written by the indexing model from the issue text.