EE: Use group clusters when deploying (DeploymentPlatform)

What does this MR do?

Updates DeploymentPlatform to use group level clusters (EE counterpart to CE Merge Request)

What are the relevant issue numbers?

https://gitlab.com/gitlab-org/gitlab-ce/issues/34758, https://gitlab.com/gitlab-org/gitlab-ce/issues/53592

Tasks

• ee/app/models/concerns/ee/deployment_platform.rb
• tests

Manual QA

• Turn on CI_DEBUG_TRACE
• Make two group cluster, * and review/*
  • Namespace and SA for project is created in each cluster
  • Add a group CI variables for AUTO_DEVOPS_DOMAIN
  • Run auto devops pipeline on master a project in the group - Expect deploy to * group clusters (check kubernetes pods)
  • Run auto devops pipeline on branch a project in the group - Expect deploy to review/* group clusters (check kubernetes pods)
  • check KUBE_TOKEN sent is restricted SA
• make two project clusters, * and review/*
  • Namespace and SA for project is created in each cluster
  • set AUTO_DEVOPS_DOMAIN variable at project level
  • Run auto devops pipeline on master - Expect deploy to project * clusters (check kubernetes pods)
  • Run auto devops pipeline on branch - Expect deploy to project review/* clusters (check kubernetes pods)
  • check KUBE_TOKEN sent is restricted SA
• Disable project review/* cluster
  • Run auto devops pipeline - Expect deploy to project * cluster (check kubernetes pods)
• Disable project * cluster
  • Run auto devops pipeline - Expect deploy to group review/* cluster (check kubernetes pods)

Deploying to * group cluster:

Does this MR meet the acceptance criteria?

• Changelog entry added, if necessary
• Documentation created/updated - https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/22804
• 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
• 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?