We are removing one-click applications from GitLab but leaving the
integrations for Prometheus and Elastic Stack.

We have code in place that keeps the integration in sync with the
corresponding cluster application, and have backfilled the
ingtegrations, so we can now use them as a source of truth.

See

- Backfill Prometheus: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/61502
- Backfill Elastic Stack: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/61521
- Deprecation Epic: https://gitlab.com/groups/gitlab-org/-/epics/4280

This commit adds a new model for the Cilium cluster
application. Related factories and specs were also updated.

DRY up a couple of places where we do so

This enables FactoryBot/FactoryClassName and FactoryBot/CreateList cops.
They were disabled in the upgrade of gitlab-styles gem because they were
causing violations.

- Adds Clusters::Cluster.with_persisted_applications scope
- Create workers to remove cluster and resources
- Ignore non existing metrics on Prometheus uninstallation
- Inform frontend of cluster removing status by the status_name attr
- Guarantee kubeclient core can delete namespace and SA
- Create cluster cleanup_status state machine
- Create cleanup_status_reason for error description

- This state machine will be used to control the flow for removing
a cluster and all of its resources. This change only deals with the
state machine, the actual functionality of removal will be implemented
on https://gitlab.com/gitlab-org/gitlab/merge_requests/16954.

Similar to the existing GCP cluster data model, introduce
models to represent an AWS user role, and an EKS cluster
that has been created by GitLab.

This association will be used for a cluster to indicate which project is
used to manage it.

Validate against duplicate scope for same project. If multiple clusters
with the same scope points to the same management_project, it will be
impossible to deterministically select a cluster

Static attributes are deprecated in FactoryBot 4.x and removed on 5.x.
https://thoughtbot.com/blog/deprecating-static-attributes-in-factory_bot-4-11

- Permits cloud_run parameter in ClustersController#create
- Enables httpLoadBalancing, istioConfig, and cloudRunConfig in
  Gcp ProvisionService if cloud_run is enabled
- Add `Enable Cloud Run on GKE` checkbox to cluster create page
- Add `Enable Cloud Run on GKE` checkbox to cluster details
- Default knative to pre_installed for cloud_run clusters
- Make knative not uninstallable for pre_installd clusters
- Update project clusters docs with entry about Cloud Run
- Update tests and add new test for cluster with cloud_run enabled
- Add Cloud Run on GKE strings to translations
- Add spec that will fail when google-api-client has been upgraded
- Add pre_installed to applications frontend
- Pass providerType and preInstalledKnative to frontend
- Display `installed via` on frontend for Cloud Run
- Add Cloud Run spec for FinalizeCreationService

Relates to https://gitlab.com/gitlab-org/gitlab/issues/27502

Kubernetes deployments on new clusters will now have
a separate namespace per project environment, instead
of sharing a single namespace for the project.

Behaviour of existing clusters is unchanged.

All new functionality is controlled by the
:kubernetes_namespace_per_environment feature flag,
which is safe to enable/disable at any time.

Using the sed script from
https://gitlab.com/gitlab-org/gitlab-ce/issues/59758

Also means we don't have to resort to an update statement to set parent
for child groups who also have clusters.

This is much shorter than

```
create(:cluster, :provided_by_gcp, :group, groups: [group])
```

When this option is enabled, GitLab will create namespaces and service
accounts as usual. When disabled, GitLab wont create any project
specific kubernetes resources

Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/56557

Adds boolean field 'managed' to clusters table. This new column will be
used to distinguish those clusters that are automatically managed by
gitlab.

Needed for https://gitlab.com/gitlab-org/gitlab-ce/issues/56557

Only create an associated project or group if there
were none already specified.

This is the 1st step for moving Auto DevOps domain into cluster
settings, whether is project or group.

Related to https://gitlab.com/gitlab-org/gitlab-ce/issues/52363

Even though we currently only should have one group for a cluster, we
allow the flexibility to associate to other groups in the future.

This also matches the runner <=> groups association.

- Adds Cluster#first_group, aliased to Cluster#group. For the
conceivable future, a cluster will have at most one group.

- Prevent mixing of group and project clusters. If project type
clusters, it should only have projects assigned.  Similarly with groups.

- Default cluster_type to :project_type. As it's very small table we can
set default and null: false in one release.

This reverts merge request !20801

- Change find_cluster_platform_kubernetes to ignore environment argument
- Fix broken specs

CE Port of: https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/5047/

- Change cluster factory to use default_environment
- Add a constant on cluster to declare default environment
- Change find_cluster_platform_kubernetes to search for a specific
  environment on EE, and ignore environment argument on CE
- Override find_cluster_platform_kubernetes and deployment_platform
  methods
- Remove memoization frmo deployment_platform on EE, otherwise when
  searching for a another platform, once the first one is assigned,
environment parameter is completely ignored

I've followed the [upgrade guide](https://github.com/thoughtbot/factory_bot/blob/4-9-0-stable/UPGRADE_FROM_FACTORY_GIRL.md) and ran these two commands:

```
grep -e FactoryGirl **/*.rake **/*.rb -s -l | xargs sed -i "" "s|FactoryGirl|FactoryBot|"
grep -e factory_girl **/*.rake **/*.rb -s -l | xargs sed -i "" "s|factory_girl|factory_bot|"
```
Signed-off-by: Rémy Coutable <remy@rymai.me>

I've followed the [upgrade guide](https://github.com/thoughtbot/factory_bot/blob/4-9-0-stable/UPGRADE_FROM_FACTORY_GIRL.md) and ran these two commands:

```
grep -e FactoryGirl **/*.rake **/*.rb -s -l | xargs sed -i "" "s|FactoryGirl|FactoryBot|"
grep -e factory_girl **/*.rake **/*.rb -s -l | xargs sed -i "" "s|factory_girl|factory_bot|"
```
Signed-off-by: Rémy Coutable <remy@rymai.me>