fix: remove the bundled registry from every host, and stop starting it

netOrk's docker-compose.yml shipped a registry:2 for the satellite image,
and this script started it on every deploy as infrastructure. Satellites
pull from registry.netork.io; on 172.22.8.50 the registry held one old
image, nothing had pulled from it in 30 days, and it accepted anonymous
pushes on port 5000 of every instance (NetOrk/netork#763).

- registry leaves INFRA_SERVICES.
- A new step removes services netOrk no longer ships: the container
  netork-registry-1, then the volume netork_registry_data. `docker
  compose up` never removes a container whose service left the compose
  file, so without this each host would keep it until someone removed it
  by hand. The step is idempotent and works with the old compose file as
  well as the new one, so it can go out before netOrk drops the service.

README.md

@@ -81,8 +81,10 @@ started earlier pulls whatever image the registry held before, which is stale.
    more after 5 s (`DEPLOY_RECREATE_RETRY_DELAY`). Compose's parallel recreate can lose
    a container it just renamed and leave the rest stopped. If the second attempt fails
    too, the container states are printed and the deploy fails.
-4. Reconciles `registry`, `apt-cacher-ng` and `signal-api`: each is recreated only if its
+4. Reconciles `apt-cacher-ng` and `signal-api`: each is recreated only if its
    definition changed. It never touches `postgres` or `redis`.
+   It then removes services netOrk no longer ships, container and volume, where a host
+   still has them: today the bundled `registry` (NetOrk/netork#763).
 5. Verifies that the containers run exactly the image that was pulled. If they don't, the
    deploy fails.
 6. Records `REGISTRY_HOST` and `NETORK_VERSION` in `~/netork/.env`, so that a