Populating the MachineConfigPool (MCP) status from MachineConfigNode (MCN) statuses previously caused some bugs, as detailed more in MCO-1228's description. To prevent this from happening again, we should implement end-to-end (e2e) tests to ensure that MCP status population is the same in the existing sync flow and in the new the Status Reporting method.

The scope of this task is to create tests to encompass the new functionality while taking special care to test the previously caught problem cases reported as part of OCPBUGS-32812 & OCPBUGS-44290.

Done when:

• There are e2e tests that encompass the new Status Reporting method of populating MCP statuses (the work implemented in MCO-1228).
• The e2e tests should build confidence for both standard and OnClusterLayering (OCL) update paths.

Important test cases (not a fully inclusive list):

• Inspired by OCPBUGS-32812: Make sure the number of updated nodes is correct on image rollout.
• Inspired by OCPBUGS-44290: Make sure degrade conditions impact MCPs as expected.
• Inspired by OCPBUGS-58198: Make sure that the number of ready & updating nodes is correct when enabling and disabling OCL.