nix: give the gateway, resolver and bridge their own enable

`services.hyperhive.gateway.enable`, `gateway.dns.enable` and
`network.enable` replace the `hyperhive.enable` gate on all three. Each
defaults to false; the modules that need one assert it with `mkDefault
true` from inside the guard their own deployment already carries, and
`swarm-required-services.nix` — the module that owns what the
swarm-services toggle implies — asserts all three explicitly.

hive-c0re asserts all three unconditionally, so an ordinary hive keeps
getting them with no opt-in: it is the host's only knowledge that agent
containers exist.

The resolver moves to its own `hive-gateway/dns.nix` so it can be gated
without reindenting the nginx half of the module.

Reinstates `network.enable`, dropping its `mkRemovedOptionModule` shim.
A config still carrying `network.enable = false` from before the removal
now switches the bridge off instead of failing eval.

Also deletes a duplicate `centralToggleOff` fixture in nix/module-eval.nix.
Two sibling slices added it independently (c5f60fd5, ce3b3d94); the merge
was textually clean and left `main` failing to evaluate at all, so this
file could not be gated without removing one.

nix/host-modules/hive-c0re/default.nix

@@ -158,6 +158,13 @@ in
   ];
 
   config = lib.mkIf cfg.enable {
+    # This module is the host's only knowledge that agent containers
+    # exist: they hang off the bridge, resolve through dnsmasq, and their
+    # UIs — plus the operator dashboard — are served by the gateway.
+    services.hyperhive.gateway.enable = lib.mkDefault true;
+    services.hyperhive.gateway.dns.enable = lib.mkDefault true;
+    services.hyperhive.network.enable = lib.mkDefault true;
+
     # The daemon that owns every container on this hive, and the helper it
     # delegates its root operations to. An agent asking why a container did
     # not come up is asking about one of these two.