Bump apimanager crd v1beta1

[eguzki]

Related links:

• https://issues.redhat.com/browse/THREESCALE-8445
• Apimanager 2.11: add preserve unknown fields #752

After installing a CRD with the new v1beta1,when in some other namespace an older operator installation is tried, OLM, happily, prevents the older installation as the old CRD does not contain all required APIs

According to official doc: https://docs.openshift.com/container-platform/4.8/operators/understanding/olm/olm-understanding-dependency-resolution.html

A CRD will be upgraded if satisfies the following condition:

All existing serving versions in the current CRD are present in the new CRD.

The OLM shows this error when trying to "downgrade" the operator CRD:

And the installation of the downgrade fails 👍 which prevents side effects described in https://issues.redhat.com/browse/THREESCALE-8445

[openshift-ci]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[codeclimate]

Analysis results are not available for those commits

View more on Code Climate.

[openshift-ci]

@eguzki: PR needs rebase.

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/test-infra repository.