Add more flexibility for Tracking Database setup
Follow up from https://gitlab.com/gitlab-org/quality/gitlab-environment-toolkit/-/merge_requests/427
Currently the Geo tracking database is configured in either one of two ways:
- Assumed to be present in database already
- Created on the secondary site's praefect database server (or normal postgres on smaller)
We should make this less coupled and allow users to point GET at any database server and have it configure this database.
Task is to make it work like the other databases - creating the database when required. It should trickle down and target Praefect's database by default but then also be overridable.