MCO to skip node that cannot be drained due to PDBs

Description:-
Generally, MCO when trying to apply updated renders to the nodes sequentially, it gets stuck on the node that can't be drained. It is possible to update other nodes that do not have PDBs set (are drainable). Let's say 2nd node can't be drained then it will get stuck at the 2nd node without updating other nodes which can be updated.

Customer's business requirement:-
The customer has a different team who takes care of PDBs and cluster upgrades. When MCO is stuck at a node. They need to call another team to temporarily evict the pod from the node and schedule them on another node. If they do so the MCO sequentially tries to update the node they just re-scheduled the pods on then they need to unset PDBs again and schedule on the previous node. This causes them to call another team (that sets PDBs) multiple times (at least two). The customer wishes to reduce this other team intervention to just once.

List any affected packages or components.
MachineConfig Operator
PodDistributionBudgets