policies: let terraform-authentik read its provider API token (#82)

## Why
terraform-authentik's provider needs an Authentik API token (`TF_VAR_authentik_token`), now sourced from Vault at `kv/service/terraform/authentik` (Makefile wiring in terraform-authentik #2). The CI role needs read access to that path.

## Change
Extend `policies/kv/service/terraform/authentik.yaml` to also grant read on `kv/data/service/terraform/authentik` for the `terraform_authentik` approle + `woodpecker_terraform_authentik` k8s role.

Reviewed-on: #82
Co-authored-by: Ben Vincent <ben@unkin.net>
Co-committed-by: Ben Vincent <ben@unkin.net>

policies/kv/service/terraform/authentik.yaml

@@ -1,9 +1,12 @@
-# Allow the Terraform Authentik runner to read OAuth2/OIDC client secrets that
-# back authentik providers. Secrets live under each target service's kv
-# namespace path (kv/kubernetes/namespace/<ns>/default/oauth-credentials) and
-# are read by the module's data.vault_kv_secret_v2 lookups.
+# Allow the Terraform Authentik runner to read:
+#  - its own Authentik API token (provider auth), and
+#  - OAuth2/OIDC client secrets that back authentik providers (per target
+#    service's kv namespace path, via the module's data.vault_kv_secret_v2).
 ---
 rules:
+  - path: "kv/data/service/terraform/authentik"
+    capabilities:
+      - read
   - path: "kv/data/kubernetes/namespace/+/default/oauth-credentials"
     capabilities:
       - read