ci: fetch vault from artifactapi instead of dnf install (#99)

## Why

CI installs vault by shelling out to `dnf install vault -y`. That reads
metadata for every enabled repo (appstream/baseos/crb/epel/ha) and downloads
the 169MB vendored vault RPM from the `unkin` repo on **every** plan/apply run
(~39s per job measured in `almalinux9-opentofu:20260606`).

## Change

- Replace `dnf install vault -y` with a pinned `curl` of the upstream vault zip
  from the artifactapi `hashicorp-releases` remote proxy, extracted with the
  image's `python3` (`python3 -m zipfile`) to `/usr/local/bin/vault`.
- Pin the version via a new `VAULT_VERSION` env var (`1.20.0`); bump the var to
  upgrade.

## Speedup

Measured in `git.unkin.net/unkin/almalinux9-opentofu:20260606`:

| approach | time |
|---|---|
| `dnf install vault -y` (current) | ~39s |
| `dnf --disablerepo='*' --enablerepo=unkin` (still pulls 169MB RPM) | ~9s |
| curl zip from artifactapi + python extract (this PR) | ~6.6s |

~32s saved per plan/apply job. The zip is cached by artifactapi after first
fetch (warm ~3s).

## Caveats

- Assumes the `almalinux9-opentofu` image ships `curl` + `python3` (both
  present in `:20260606`).
- Relies on the existing artifactapi `hashicorp-releases` generic remote whose
  patterns already allow `vault/.*vault_.*_linux_amd64.zip`.

---------

Co-authored-by: benvin <neotheo@gmail.com>
Reviewed-on: #99
Co-authored-by: Ben Vincent <ben@unkin.net>
Co-committed-by: Ben Vincent <ben@unkin.net>

.woodpecker/apply.yaml

@@ -7,8 +7,9 @@ steps:
     image: git.unkin.net/unkin/almalinux9-opentofu:20260606
     environment:
       VAULT_AUTH_METHOD: kubernetes
+      VAULT_VERSION: "1.20.0"
     commands:
-      - dnf install vault -y
+      - curl -fsSL -o /tmp/vault.zip "https://artifactapi.k8s.syd1.au.unkin.net/api/v1/remote/hashicorp-releases/vault/$${VAULT_VERSION}/vault_$${VAULT_VERSION}_linux_amd64.zip" && python3 -m zipfile -e /tmp/vault.zip /tmp/ && install -m0755 /tmp/vault /usr/local/bin/vault && rm -f /tmp/vault.zip /tmp/vault /tmp/LICENSE.txt
       - make plan
       - make apply
     backend_options:

.woodpecker/plan.yaml

@@ -6,8 +6,9 @@ steps:
     image: git.unkin.net/unkin/almalinux9-opentofu:20260606
     environment:
       VAULT_AUTH_METHOD: kubernetes
+      VAULT_VERSION: "1.20.0"
     commands:
-      - dnf install vault -y
+      - curl -fsSL -o /tmp/vault.zip "https://artifactapi.k8s.syd1.au.unkin.net/api/v1/remote/hashicorp-releases/vault/$${VAULT_VERSION}/vault_$${VAULT_VERSION}_linux_amd64.zip" && python3 -m zipfile -e /tmp/vault.zip /tmp/ && install -m0755 /tmp/vault /usr/local/bin/vault && rm -f /tmp/vault.zip /tmp/vault /tmp/LICENSE.txt
       - make plan
     backend_options:
       kubernetes:

config/auth_approle_role/approle/terraform_enc.yaml

@@ -0,0 +1,9 @@
+token_ttl: 120
+token_max_ttl: 120
+bind_secret_id: false
+token_bound_cidrs:
+  - "10.10.12.200/32"
+  - "198.18.25.102/32"
+  - "198.18.26.91/32"
+  - "198.18.27.40/32"
+use_deterministic_role_id: true

config/auth_kubernetes_role/k8s/au/syd1/woodpecker_terraform_enc.yaml

@@ -0,0 +1,7 @@
+bound_service_account_names:
+  - terraform-enc
+bound_service_account_namespaces:
+  - woodpecker
+token_ttl: 600
+token_max_ttl: 600
+audience: https://kubernetes.default.svc.cluster.local

config/consul_secret_backend_role/consul_root/au/syd1/terraform-enc.yaml

@@ -0,0 +1,5 @@
+consul_roles:
+  - terraform-enc
+ttl: 120
+max_ttl: 300
+datacenters: []

policies/consul_root/au/syd1/creds/terraform-enc.yaml

@@ -0,0 +1,14 @@
+# Allow the terragrunt-enc runner to generate credentials for the
+# terraform-enc role in consul (used to lock/write its terragrunt state under
+# infra/terraform/enc/ on the consul backend).
+---
+rules:
+  - path: "consul_root/au/syd1/creds/terraform-enc"
+    capabilities:
+      - read
+
+auth:
+  approle:
+    - terraform_enc
+  k8s/au/syd1:
+    - woodpecker_terraform_enc

policies/kv/service/terraform/enc-encapi-environment.yaml

@@ -0,0 +1,14 @@
+# Allow the terragrunt-enc runner to read the encapi environment secret
+# (ENCAPI_WRITE_TOKEN), so `make apply` can write ENC data (statuses, roles,
+# nodes) to encapi via the encapi Terraform provider.
+---
+rules:
+  - path: "kv/data/kubernetes/namespace/encapi/default/environment"
+    capabilities:
+      - read
+
+auth:
+  approle:
+    - terraform_enc
+  k8s/au/syd1:
+    - woodpecker_terraform_enc

policies/kv/service/terraform/incus-encapi-environment.yaml

@@ -1,12 +0,0 @@
-# Allow the Terraform Incus runner to read the encapi environment secret
-# (ENCAPI_WRITE_TOKEN), so `make apply` can dual-write ENC data to encapi via
-# the encapi Terraform provider.
----
-rules:
-  - path: "kv/data/kubernetes/namespace/encapi/default/environment"
-    capabilities:
-      - read
-
-auth:
-  approle:
-    - terraform_incus

resources/secret_backend/consul_root/au/syd1/terraform-enc.hcl

@@ -0,0 +1,7 @@
+key_prefix "infra/terraform/enc/" {
+  policy = "write"
+}
+
+session_prefix "" {
+  policy = "write"
+}