nix: gate hive-c0re on deploy.hive-controller.enable, drop hyperhive.enable

`services.hyperhive.enable` and `services.hyperhive.c0re.enable` are gone.
One switch, `services.hyperhive.deploy.hive-controller.enable` (default
false, as the old toggle was), now gates hive-c0re and hive-priv. Both old
paths are `mkRenamedOptionModule` shims in deploy.nix, so a host config
that still sets either evaluates as before and gets a rename warning.

Every other read of the old toggle is resolved, including the 29 made
through the `hyperhiveCfg`/`hiveCfg` aliases:

- Dropped: each swarm service and its glue keeps only its own deploy
  toggle (authelia, bao and its PKI glue, grafana, victorialogs,
  victoriametrics, the secret publisher, swarm-ca, the OIDC client rows,
  the controller/nats/matrix-ctl/publisher/services-issuer identities),
  the forge, and the `domain` deprecation warning.
- To deploy.hive-controller.enable: the queue-agent credential reader and
  its assertion, which feed hive-c0re and write under its state dir, plus
  their policy-order entry; the network identity assertions; hive-tls's
  two writes into hive-c0re's environment.
- hive-tls runs where the gateway runs self-signed
  (`gateway.enable && useSelfSigned`), not on every host.
- The matrix appservice-token reader and its assertion stay on
  `deploy.matrix.enable` plus their client-identity checks. They read
  deploy.matrix's token file and registration script; their deploy.bao
  inputs are the client-half options a hive sets to read a store it does
  not run, so gating on deploy.bao.enable would drop the tested
  remote-reader case.
- The `hiveName` assertion moves from hive-network.nix to hyperhive.nix
  and fires wherever the hive, the store or the homeserver runs: each
  turns the name into an identifier with no fallback.

On a host with `deploy.allSwarmServices` and no hive, the documented
services-host recipe, authelia, bao, grafana, victorialogs,
victoriametrics, the OIDC client rows and the hive CA now render; before,
the old toggle being off left them out.

Refs #4500

nix/host-modules/swarm-wireguard.nix

@@ -84,13 +84,11 @@
     };
   };
 
-  # Gated on the mesh itself, NOT on the c0re daemon. The mesh is host
-  # networking, not a c0re feature: a swarm host that runs no hive —
-  # the snapshot store, for one — still has to join the mesh, and under
-  # the old `c0re.enable` gate it silently got no `wg-hive` interface
-  # at all. Nothing below is c0re-specific; the peer data c0re consumes
-  # (HIVE_PEER_CA_PATHS) is rendered in ./hive-c0re and stays gated
-  # there.
+  # Gated on the mesh itself, NOT on `deploy.hive-controller.enable`. The
+  # mesh is host networking, not a c0re feature: a swarm host that runs no
+  # hive — the snapshot store, for one — still has to join the mesh.
+  # Nothing below is c0re-specific; the peer data c0re consumes
+  # (HIVE_PEER_CA_PATHS) is rendered in ./hive-c0re and stays gated there.
   config = lib.mkIf config.services.hyperhive.deploy.wireguard.enable {
     assertions = [
       {