Have relprep.sh check to see if bundle & manifest CSVs are in sync

[joelsmith]

Also:

• make CRD extraction more robust, to handle more than just examples.keda.sh CRDs
• notice when there are missing CRDs in the bundle generation inputs
• manually sync some of the manifest CSV fields and the inputs to the
  generated bundle CSV's fields so that the new check passes

Checklist

• Commits are signed with Developer Certificate of Origin (DCO)

Notes for reviewers:
While doing the upstream 2.12.1 release, I noticed a little weirdness in the KEDA OLM operator's hack/relprep.sh script. Namely, that it isn't keeping config/manifests/bases/keda.clusterserviceversion.yaml and bundle/manifests/keda.clusterserviceversion.yaml in sync. Apparently, the former doesn't get updated by the operator-sdk generate kustomize manifests -q command like I thought it did, and the latter does get updated, but is only used for our manual testing workflow (when we're developing or doing a release). While playing around with it, I also did some test runs on 2.13.0 and noticed that there is a new CRD coming our way which lives in eventing.keda.sh instead of keda.sh, so that also broke the script. So I've opened a PR to "fix" all of that. I'm using quotes because some of the things aren't actually fixed by the script, only detected, so that a human knows which things to manually update. I didn't figure it was worth the work to automate them at this point, but we can always change our mind later if I'm wrong.

[joelsmith]

Changes to config/manager/manager.yaml and the resulting generated changes to bundle/manifests/keda.clusterserviceversion.yaml are to make them match

keda-olm-operator/config/manifests/bases/keda.clusterserviceversion.yaml

Lines 632 to 633 in 46bdc56

	securityContext:
	runAsNonRoot: true

and

keda-olm-operator/config/manifests/bases/keda.clusterserviceversion.yaml

Lines 623 to 627 in 46bdc56

	securityContext:
	allowPrivilegeEscalation: false
	capabilities:
	drop:
	- ALL

The change to add a label in config/manifests/bases/keda.clusterserviceversion.yaml is to make it match the bundle-generated CSV.

[jkyros]

Thanks for the detail and background, very much appreciated.

Oh yuck, and you had to change the keda.yaml parsing too. Chores have been rough this round 😄

/lgtm