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-bao.nix

@@ -1573,7 +1573,7 @@ in
     # they still fire when the cert paths are unset — the arm below is not
     # evaluated in that case, and an assertion that disappears exactly when
     # its subject is broken would be worse than none.
-    (lib.mkIf (hyperhiveCfg.enable && deployCfg.bao.enable) {
+    (lib.mkIf deployCfg.bao.enable {
       assertions = [
         {
           assertion = lib.versionOlder baoDeploy.package.version "2.7.0";
@@ -1655,7 +1655,7 @@ in
       services.hyperhive.network.enable = lib.mkDefault true;
     })
 
-    (lib.mkIf (hyperhiveCfg.enable && deployCfg.bao.enable) {
+    (lib.mkIf deployCfg.bao.enable {
       # The wrapper alone, never `baoDeploy.package`: openbao's own module
       # installs the CLI *inside* the container, and this host had none at all,
       # so an operator either hopped into the container or re-typed the
@@ -1845,7 +1845,7 @@ in
       };
     })
 
-    (lib.mkIf (hyperhiveCfg.enable && deployCfg.bao.enable && haveServerTls) {
+    (lib.mkIf (deployCfg.bao.enable && haveServerTls) {
       # Provisions the TPM-backed token the seal above names. One-shot and
       # idempotent on ABSENCE, never on content: regenerating a PIN would
       # orphan an already-sealed store, so a rebuild must not rotate it.