Docs: Refactor "cluster levels"

Problem to solve

Reword what we call "cluster levels" as this is just a legacy term used internally at GitLab. The term is not part of the industry terminology.

Proposal

  • Remove the 3 pages (project level, group level, instance level).
  • Highlight only that the user can connect a cluster in different "scopes" (should we use this term?) meant for different interactions with GitLab:
    • Connect to a project - to use the cluster with one single project.
    • Connect to a group - to use the cluster in projects within a group.
    • Connect to an instance - to use the cluster in all projects within the instance.
  • Indicate the availability of each feature according to each scope.

Who can address the issue

~"devops::configure"

ETA: %14.5 ish

Other links/references

Let's include into the content review epic: &6267