have the CVO manage CRDs from the api image

[deads2k]

Full chain is

1. have the CVO manage CRDs from the api image #1666
2. yield CRDs and empty resource rendering to api imge cluster-config-operator#379
3. Skip cluster config installer#7666
4. read featuregates from openshift/api cluster-config-operator#349
5. create manifest directory during rendering cluster-config-operator#382
6. Allow split rendering between cluster-config and openshift/api cluster-config-operator#380
7. create parent dir for output cluster-config-operator#381
8. catch another non-yaml tolerant call #1669
9. Allow split rendering between cluster-config and openshift/api cluster-config-operator#380
10. fix improper cast in render #1665
11. make the render read yaml properly #1662
12. bring openshift/api into the payload #1642
13. add image build for openshift/api release#43522
14. update to rhel9 for image build #1635
15. add cluster-config-api component mapping openshift-eng/ocp-build-data#3778
16. Image and manifests #1567

/hold

must merge together with openshift/cluster-config-operator#379

While the vendored level in cluster-config-operator matches, these can show green simultaneously. When that happens, we need to manually merge both to avoid future conflicts.

[openshift-ci]

Hello @deads2k! Some important instructions when contributing to openshift/api:
API design plays an important part in the user experience of OpenShift and as such API PRs are subject to a high level of scrutiny to ensure they follow our best practices. If you haven't already done so, please review the OpenShift API Conventions and ensure that your proposed changes are compliant. Following these conventions will help expedite the api review process for your PR.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: deads2k

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 [deads2k]

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

[openshift-ci]

@deads2k: all tests passed!

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.

[deads2k]

launch openshift/cluster-config-operator#379,#1666 worked

[deads2k]

openshift/installer#7666 switching the installer rendering to use openshift/api has tested green and is ready to make the switch

#1666 and openshift/cluster-config-operator#379 have clusterbot tested together fine. They hand off the CVO management of CRDs (and others) from cluster-config-operator to api image.

openshift/cluster-config-operator#349 switches the featuregate setting from using the vendored copy from to using openshift/api. It tested green until it openshift/api updated without a (yet) merged openshift/cluster-config-operator update, so the machine-config-operator mismatched until they rematch. But in combination with the rendering change linked above they will match ok.

Manually merging to get a batch.

[openshift-bot]

[ART PR BUILD NOTIFIER]

This PR has been included in build ose-cluster-config-api-container-v4.15.0-202311291533.p0.ga782d1c.assembly.stream for distgit ose-cluster-config-api.
All builds following this will include this PR.