While prepping for my demo to the testing team, I ran into a few issues.
These did not come up earlier as I was using an incomplete method for
nuking my local openQA install to test this automation.
- Check for Postgres data directory now correctly checks for a `base`
dir rather than its parent `data` (which can exist but be empty if
Postgres has been installed but not initialized
- firewalld service is named `http`, not `httpd`
- Automation now "logs in" to web UI, allowing fifloader.py to execute
* Add automation for bootstrapping an openQA developer box
This PR adds the playbook `init-rocky-openqa-developer-host.yml`, to be
used for bootstrapping developer instances of OpenQA. This playbook
mostly follows the automation from [this
repo](https://github.com/rocky-linux/OpenQA-Fedora-Installation).
* Add suggestions from @nazunalika
