Discussed with @alculquicondor offline, another option is to run `nodeSchedulingPropertiesChange` unconditionally.    The slight difference with old behavior is: the new behavior increments moveRequestCycle when node properties changes, no matter there is unschedulable pods or not; while in old logic, moveRequestCycle can be incremented when node properties don't change but no unschedulable pods are present.