Only enable the tracking database when in a secondary site

What does this merge request do and why?

This restores the GDK primary behavior to not include the Geo Tracking Database, as it's available only on the secondary site in a production environment.

Since we've migrated to use the rails multi database support, there isn't a way to keep the tracking database only in the test environment anymore, see: #1811 (comment 1586805193)

This are the changes introduced by this MR:

• remove the geo: section from the database.yml in a GDK primary site.
• disables postgresql-geo in a GDK primary site.
• ensure postgresql is restarted when port changes (required for the Geo install)

Fixes #1811 (closed) #1952 (closed)

To the maintainer:

This has been tried before via: !3113 (merged) which got reverted by: !3158 (merged) due to it including some side-effects, documented here: #1816 (closed)

How to set up and validate locally

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

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.