Resolve "ee:geo QA specs are failing as of !7210"

What does this MR do?

Resolves a race condition in Geo Nodes API spec vs GeoNodeStatus creation, by making the spec wait until they are created.

I believe it is reasonable for Geo node statuses to not exist on first startup. For performance reasons, it is not reasonable to update any status synchronously. We attempt to update the status every minute, so this initial condition goes away quickly.

• Removes most tests in Geo Nodes API QA spec that are redundant with tests in the Geo Nodes request spec.
• Adds to the Geo Nodes request spec to explicitly define behavior when 1 vs 2 geo node statuses exist
• Avoids the race condition that caused failing tests

What are the relevant issue numbers?

• Resolves https://gitlab.com/gitlab-org/gitlab-ee/issues/7434
• Resolves https://gitlab.com/gitlab-org/quality/nightly/issues/7

Does this MR meet the acceptance criteria?

• Changelog entry added, if necessary
• Documentation created/updated
• Tests added for this feature/bug
• Conforms to the code review guidelines
• Conforms to the merge request performance guidelines
• Conforms to the style guides
• Conforms to the database guides
• 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?