Geo: Help admins diagnose configuration problems

What does this MR do?

When Geo is misconfigured, or some infrastructure is not healthy, we display some health checks on Admin > Geo > Nodes. But the information is often cryptic and not too helpful. A good first step is to run gitlab-rake gitlab:geo:check.

• This MR adds a Geo Troubleshooting doc link beneath Geo Node errors.
• This MR adds the gitlab-rake gitlab:geo:check command to the Geo Troubleshooting doc.

What are the relevant issue numbers?

Resolves https://gitlab.com/gitlab-org/gitlab-ee/issues/10342

Does this MR meet the acceptance criteria?

• Changelog entry added, if necessary
• Documentation created/updated via this MR
• Documentation reviewed by technical writer or follow-up review issue created
• Tests added for this feature/bug
• Tested in all supported browsers
• Conforms to the code review guidelines
• Conforms to the merge request performance guidelines
• Conforms to the style guides
• Conforms to the database guides
• ~~Link to e2e tests MR added if this MR has Requires e2e tests label. See the Test Planning Process.~~
• EE specific content should be in the top level /ee folder
• For a paid feature, have we considered GitLab.com plans, how it works for groups, and is there a design for promoting it to users who aren't on the correct plan?
• Security reports checked/validated by reviewer