Prevent k8s version skew policy violations due to clusterctl rollout undo

[hiromu-a5a]

The existing clusterclt rollout undo command might violate the version skew policy easily and accidentally. For example, if a user has MachineSet (revision=1, k8s version=1.22) and MachineSet (revision=4, k8s version=1.25) and mistakenly triggers rollback from revision 4 to 1, there's no way to stop it. I'd like to suggest that clusterctl raises an error if users break the version skew policy and allow the operation only if a user sets --force option. What do you think?