Replace long running collect-profiles jobs

Problem: The collect-profiles job should only take a few seconds to
run. There are instances, such as when the pod cannot be scheduled,
where the job will not complete in a reasonable amount of time. If
enough jobs are scheduled but unable to run, the number of
scheduled jobs can exceed pod quota limits.

Solution: Given that the collect-profiles job should only take a few
seconds to run and that the job is scheduled to run every 15 minutes,
set the collect-profiles cronJob's spec.concurrencyPolicy to
"Replace" so that only one active collect-profiles pod exists at any
time.

Author: awgreene

manifests/0000_50_olm_07-collect-profiles.cronjob.yaml

@@ -8,6 +8,7 @@ metadata:
   namespace: openshift-operator-lifecycle-manager
 spec:
   schedule: "*/15 * * * *"
+  concurrencyPolicy: "Replace"
   jobTemplate:
     spec:
       template:

scripts/generate_crds_manifests.sh

@@ -247,6 +247,7 @@ metadata:
   name: collect-profiles
   namespace: openshift-operator-lifecycle-manager
 spec:
+  concurrencyPolicy: "Replace"
   schedule: "*/15 * * * *"
   jobTemplate:
     spec: