Why:
- The netbox secrets engine mount + roles land in a follow-up PR; its manage
policy must exist first so the deployer can create the config and roles the
moment the engine PR applies (policy-first split).
How:
- Add policies/netbox/admin.yaml granting the deployer netbox/config,
netbox/config/rotate and netbox/roles/* (excludes netbox/creds/*), bound to
the tf_vault AppRole and woodpecker_terraform_vault k8s role, mirroring the
gpg/gitea admin policies.