1. Proposed title of this feature request

MCO should allow mcp to recover if the reason it's degraded is due to files that are affected by a new MC

2. What is the nature and description of the request?

Sometimes installation/upgrade process requires touching files that are managed by MCO before mco is running.

After applying new content via machine config MCO should be able to heal itself.

Example: 

Image-Based-Installation and Image-Based-Upgrade requires, in certain conditions, changing pull-secret or registry-config before cluster starts, this causes mcp to finish in degraded state and there is not way to recover. 

 3. Why does the customer need this? (List the business requirements here)

Will allow MCO self-healing and not stuck in degraded pool forever
4. List any affected packages or components.

Machine-Config-Operator