Revert "only add geo tracking database to database.yml when in a secondary site"

What does this merge request do and why?

Reverts !3113 (merged) to resolve #1816 (closed) until we find a better resolution for #1811 (closed).

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

1. Set up 2 GDKs with Geo
2. Run make geo-primary-update

Before this MR, you would see the error in #1816 (closed)

With this MR, the error would not occur.

Impacted categories

The following categories relate to this merge request:

• gdk-reliability - e.g. When a GDK action fails to complete.
• gdk-usability - e.g. Improvements or suggestions around how the GDK functions.
• gdk-performance - e.g. When a GDK action is slow or times out.

Merge request checklist

• This change is backward compatible. If not, please include steps to communicate to our users.
• [-] Tests added for new functionality. If not, please raise an issue to follow-up.
• [-] Documentation added/updated, if needed.
• [-] Announcement added, if change is notable.
• [-] gdk doctor test added, if needed.
• [-] Add the ~highlight label if this MR should be included in the CHANGELOG.md.