Fix: scheduler: a failed migrate_to always matters for the target if the resource has no newer state there

The previous check on whether there's a stop operation happened after
any migrate_from on the target was not actually reliable/sensible, since
there's unlikely a migrate_from there given that the migrate_to has
failed here first of all.

This commit correctly handles the test case
not-reschedule-unneeded-monitor.