Move deployment/deploy-openbao-kayobe-automation.yml to secret-store/…

[maxstack]

Fixes openbao deployment issues on GitHub runner.
Also moves this deploy playbook into the secret-store ansible location alongside its unseal counterpart.

Chages made:

• generally define all variables similarly to the seed and overcloud deploy playbooks
• use docker0 network interface for GitHub as the kayobe automation containers can't contact the host's localhost
• keep the network interface as lo for Gitlab deployments, which seems to be where this playbook was working
• fix api_url adding missing protocol

[gemini-code-assist]

Code Review

This pull request integrates OpenBao as a secret store for GitHub and GitLab CI/CD workflows. It updates the documentation to guide users on deploying OpenBao, configuring workflows to retrieve secrets, and managing secrets/variables based on whether OpenBao is used. The Ansible playbooks for deploying and unsealing OpenBao on runners have been modified to dynamically configure network interfaces and standardize paths. Review feedback indicates that the vault_unseal_verify: false parameter is commented out in both the deploy and unseal playbooks, which could lead to failures with self-signed certificates. Additionally, a phrase in the documentation regarding 'add network IP' needs clarification, and the table for secrets when OpenBao is not used is incorrect, as it redundantly includes REGISTRY_PASSWORD and omits KAYOBE_VAULT_PASSWORD. Finally, the vault_unseal_token is unnecessarily included in the unseal playbook.