Mount the gpg engine and manage a 'pass' key

Mount the gpg secrets engine (the plugin is registered separately via the
plugin module + config/plugins, #89) and manage OpenPGP keys with the
gpgvaultsecret provider.

- gpg_secret_backend module: mounts the registered plugin type; depends_on the
  plugin module so the mount waits for catalog registration.
- gpg_key module (via the gpgvaultsecret provider, registered in root.hcl):
  create/configure keys; wired through vault_cluster + config discovery
  (config/gpg_key/<backend>/<name>.yaml).
- config/gpg_secret_backend/gpg.yaml mounts at gpg/; config/gpg_key/gpg/pass.yaml
  is an rsa-4096 'pass' key for password-store (private key stays in Vault;
  clients decrypt via gpg/decrypt/pass).

Rebased onto master after the access (#88) and plugin-import (#89) PRs merged.

modules/vault_cluster/variables.tf

@@ -327,6 +327,29 @@ variable "plugins" {
   default = {}
 }
 
+variable "gpg_secret_backend" {
+  description = "Map of GPG/OpenPGP secret engines to mount (path => registered plugin + description). The plugin is registered separately via config/plugins."
+  type = map(object({
+    plugin      = optional(string, "vault-plugin-secrets-gpg")
+    description = optional(string)
+  }))
+  default = {}
+}
+
+variable "gpg_key" {
+  description = "Map of OpenPGP keys to manage in a gpg engine mount"
+  type = map(object({
+    name                   = string
+    backend                = string
+    algorithm              = optional(string, "rsa-3072")
+    identity               = optional(string)
+    exportable             = optional(bool, false)
+    deletion_allowed       = optional(bool, false)
+    min_decryption_version = optional(number)
+  }))
+  default = {}
+}
+
 variable "policy_auth_map" {
   description = "Map of auth mounts -> auth roles -> policy names"
   type        = map(map(list(string)))