How to set Machine Config Operator into unmanaged state

Issue

During troubleshooting a Red Hat Support Engineer has requested changes be performed to the Machine Config Operator (MCO) configurations and deployments. These resources are controlled by the Cluster Machine Config Operator, which manages most of the resources within the openshift-machine-config-operator Namespace.

The Cluster Version Operator (CVO) manages the Machine Config Operator deployment and therefore it the MCO must be removed from the CVO management before any changes to the Operator or its managed resources can be performed.

NOTE: This should not be performed without the request of an Red Hat OpenShift Support Engineer and will result in the OpenShift Cluster in an unsupported state