crd-schema-check: allow new CRDs

[dprince]

If the 'git show BASE_REF' fails assume it is a net new CRD and should be fine.

[softwarefactory-project-zuul]

Build failed (check pipeline). Post recheck (without leading slash)
to rerun all jobs. Make sure the failure cause has been resolved before
you rerun jobs.

https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/ff3d3130dbc44c73b75ce5b3f66747e5

✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 36m 47s
✔️ podified-multinode-edpm-deployment-crc SUCCESS in 1h 21m 52s
❌ cifmw-crc-podified-edpm-baremetal RETRY_LIMIT in 13m 36s
❌ openstack-operator-tempest-multinode RETRY_LIMIT in 7m 28s

[gibizer]

@dprince Thanks for fixing. This was an oversight on my part. I agree that if the base version does not have the CRD defined then the CRD is not a subject of any backward compatibility issues

[gibizer]

pre-commit failures are relevant

bashate..................................................................Failed
- hook id: bashate
- exit code: 1
hack/crd-schema-checker.sh:20:1: E003 Indent not multiple of 4
hack/crd-schema-checker.sh:20:1: E003 Indent not multiple of 4
hack/crd-schema-checker.sh:20:1: E003 Indent not multiple of 4
3 bashate error(s) found

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dprince, gibizer

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [dprince]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[bogdando]

lgtm

[dprince]

/test openstack-operator-build-deploy-kuttl