Move k8s-workloads projects to a dedicated runner

As a corrective action for production#3180 (closed) we will move projects to the existing ops runnerrunner-01-sv-ops.c.gitlab-ops.internal` :

Note that on ops we decided not to do any project restrictions based on the runner tag, instead we will have a release tag (for deployer) and a k8s-workloads tag for k8s.

• Unpause runner-01-sv-ops.c.gitlab-ops.internal in ops admin
• Tag runner-01-sv-ops.c.gitlab-ops.internal with k8s-workload
• Terraform change to give access to the k8s cluster for the ops runner https://ops.gitlab.net/gitlab-com/gitlab-com-infrastructure/-/merge_requests/2247
  • Staging tf apply -target module.gke-us-east1-b -target module.gke-us-east1-c -target module.gke-us-east1-d -target module.gitlab-gke
  • Ops tf apply -target module.gitlab-gke
  • Org-ci tf apply -target module.gitlab-gke
  • Production tf apply -target module.gke-us-east1-b -target module.gke-us-east1-c -target module.gke-us-east1-d -target module.gitlab-gke
• Tanka switchover gitlab-com/gl-infra/k8s-workloads/tanka-deployments!84 (merged)
• k8s-workloads gitlab-com/gl-infra/k8s-workloads/common!84 (merged) gitlab-com/gl-infra/k8s-workloads/gitlab-com!595 (merged)
• Runbooks switchover gitlab-com/runbooks!3054 (merged)
• woodhouse: woodhouse!68 (merged)
• helicopter: helicopter!4 (merged)