Remove unused yaml in cvo to speed up reconciliation

[lance5890]

1. Extract the release image from ocp-release:4.20.0-ec.3, found that there are a few unused yaml in the 4.20 version, as follows:

grep -rn "release.openshift.io/delete" ./release-manifests/*
./0000_26_cloud-controller-manager-operator_10_deployment_tombstone.yaml:10:    release.openshift.io/delete: "true"
./0000_30_cluster-api_10_webhooks.yaml:112:    release.openshift.io/delete: "true"
./0000_50_cloud-credential-operator_01-service-delete.yaml:7:    release.openshift.io/delete: "true"
./0000_50_cluster-autoscaler-operator_99_tombstones.yaml:8:    release.openshift.io/delete: "true"
./0000_50_cluster-autoscaler-operator_99_tombstones.yaml:18:    release.openshift.io/delete: "true"
./0000_50_cluster-storage-operator_ibm-cloud-managed-cleanup.yaml:10:    release.openshift.io/delete: "true"
./0000_50_cluster-storage-operator_ibm-cloud-managed-cleanup.yaml:21:    release.openshift.io/delete: "true"
./0000_50_cluster-storage-operator_ibm-cloud-managed-cleanup.yaml:32:    release.openshift.io/delete: "true"
./0000_50_cluster-storage-operator_ibm-cloud-managed-cleanup.yaml:43:    release.openshift.io/delete: "true"
./0000_50_cluster-storage-operator_ibm-cloud-managed-cleanup.yaml:54:    release.openshift.io/delete: "true"
./0000_50_cluster-storage-operator_ibm-cloud-managed-cleanup.yaml:65:    release.openshift.io/delete: "true"
./0000_50_cluster-storage-operator_ibm-cloud-managed-cleanup.yaml:76:    release.openshift.io/delete: "true"
./0000_50_cluster-storage-operator_ibm-cloud-managed-cleanup.yaml:87:    release.openshift.io/delete: "true"
./0000_50_cluster-storage-operator_ibm-cloud-managed-cleanup.yaml:98:    release.openshift.io/delete: "true"
./0000_50_console-operator_ocs-install-tour-quickstart.yaml:10:    release.openshift.io/delete: "true"
./0000_50_olm_11-olm-operators.configmap.removed.yaml:7:    release.openshift.io/delete: "true"
./0000_50_olm_12-olm-operators.catalogsource.removed.yaml:7:    release.openshift.io/delete: "true"
./0000_50_olm_14-packageserver.subscription.removed.yaml:7:    release.openshift.io/delete: "true"
./0000_70_cluster-network-operator_02_rbac.yaml:33:    release.openshift.io/delete: "true"
./0000_90_cluster-authentication-operator_03_prometheusrule.yaml:10:    release.openshift.io/delete: "true"
./0000_90_kube-apiserver-operator_04_servicemonitor-apiserver.yaml:259:    release.openshift.io/delete: "true"
./0000_90_kube-apiserver-operator_05_api_performance_dashboard.yaml:3340:    release.openshift.io/delete: "true"
./0000_90_machine-config_90_deletion.yaml:11:    release.openshift.io/delete: "true"

2. we have to analysis every exact yaml to decide which should be reserved and which should be removed
3. As the cvo reconcile all these yamls in the directory, and too many unused yamls will cost memory consumption, remove these yamls will to do some help to speed ​​up the reconcile too in the 'permute-flatten-by-number-and-component' model

The following are the related PRs:

• cluster-etcd-operator NO-JIRA: remove grafana-dashboard-etcd cluster-etcd-operator#1429
• cluster-samples-operator OCPBUGS-57298: rm hello-openshift yaml  cluster-samples-operator#642
• cluster-kube-apiserver-operator NO-JIRA: remove unused yaml cluster-kube-apiserver-operator#1856
• cluster-network-operator NO-JIRA: remove unused clusterrolebinding default-account-cluster-network-operator cluster-network-operator#2725
• cluster-capi-operator NO-JIRA: Remove manifest for validating-webhook-configuration cluster-capi-operator#324
• cluster-cloud-controller-manager-operator NO-JIRA: Remove old deployment which is deleted cluster-cloud-controller-manager-operator#393
• cluster-autoscaler-operator NO-JIRA: Remove tombstones yamls cluster-autoscaler-operator#348
• console-operator NO-JIRA: Remove ocs-install-tour console-operator#1003
• operator-framework-olm NO-JIRA: Remove deleted yamls operator-framework-olm#1032
• cluster-storage-operator NO-JIRA: Remove ibm-cloud-managed-cleanup yaml cluster-storage-operator#586
• machine-config-operator NO-JIRA: remove default ServiceAccount which is deleted machine-config-operator#5130
• cloud-credential-operator NO-JIRA: Remove deleted service yaml cloud-credential-operator#880

[lance5890]

@petr-muller @wking

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci]

@openshift-bot: Closing this issue.

Details

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.