Fix: scheduler: don't schedule a dangling migration stop if one already occurred

See the 2020-08-18 thread to the users@clusterlabs.org list
"why is node fenced ?". If a node had a dangling migration, later had a
successful stop to recover, and is now shutting down, the scheduler would
schedule another stop, which would be unrunnable due to the shutdown, causing
unnecessary fencing.