[WIP] MCO-1457: Reintroduce MCS CA rotation

[djoshy]

This PR re-applies the work done in #4669, which was reverted in #4713. We should only land this after openshift/installer#9309

How to verify:
In addition to passing existing e2es and verification done in #4669 , agent installations should succeed. The recently added test in the MCO repo which tests agent workflows(ci/prow/e2e-agent-compact-ipv4) should give us a good signal on this.

[openshift-ci-robot]

@djoshy: This pull request references MCO-1457 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.19.0" version, but no target version was set.

In response to this:

This PR does the following:

• Re-applies the work done in MCO-643: MCO-645: Implement a rotation mechanism for the MCS TLS cert #4669, which was revert in OCPBUGS-44832: Revert MCS CA rotation #4713
• Implements generation of the MCS CA/cert during bootstrap, this should help

How to verify:
In addition to passing existing e2es and verification done in #4669 , agent installations should succeed. The recently added test in the MCO repo which tests agent workflows(ci/prow/e2e-agent-compact-ipv4) should give us a good signal on this.

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 openshift-eng/jira-lifecycle-plugin repository.

[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

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: djoshy

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

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

[openshift-ci-robot]

@djoshy: This pull request references MCO-1457 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.19.0" version, but no target version was set.

In response to this:

This PR re-applies the work done in #4669, which was reverted in #4713. We should only land this after openshift/installer#9309

How to verify:
In addition to passing existing e2es and verification done in #4669 , agent installations should succeed. The recently added test in the MCO repo which tests agent workflows(ci/prow/e2e-agent-compact-ipv4) should give us a good signal on this.

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 openshift-eng/jira-lifecycle-plugin repository.

[djoshy]

/testwith openshift/machine-config-operator/master/e2e-agent-compact-ipv4 #4735 openshift/installer#9309