Split TCP and TLS connectivity testing in Geo database configuration

What does this MR do?

Splits the TCP and TLS connectivity tests.

Are there points in the code the reviewer needs to double check?

rake gitlab:tcp_check was introduced into CE in https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/15759/diffs - we should wait until it has made its way to EE before merging this MR.

Why was this MR needed?

Checking TCP and TLS separately allows for easier debugging of problems.

Screenshots (if relevant)

Does this MR meet the acceptance criteria?

• Changelog entry added, if necessary
• Documentation created/updated
• Has been reviewed by Documentation
• Conform by the merge request performance guides
• Conform by the style guides
• Squashed related commits together
• Internationalization required/considered
• If paid feature, have we considered GitLab.com plan and how it works for groups and is there a design for promoting it to users who aren't on the correct plan

What are the relevant issue numbers?

Closes #4240 (closed)