Bugfix for capture guiding deviation recovery

When capturing is suspended after a guiding deviation, it occurs in some cases that recovery from the guiding deviation triggers multiple starts of capture with the effect that more than one capture sequence line is marked as "Running".

The problem only occurs, when the exposure start delay is longer than the guiding exposure duration.

To reproduce this, start a profile with simulators (implemented in TestEkosCaptureWorkflow::testGuidingDeviationSuspendingCapture()):

• Slew to an arbitrary target (necessary so that guiding works)
• Start guiding, preferably with a short exposure time (e.g. 1 sec)
• Create an RGB sequence each with the delay a multiple of the guiding exposure time (e.g. 5 sec) and a guiding deviation limit (e.g. 2")
• Start the sequence
• Send a guide motion pulse of 2sec through the INDI panel to simulate a guide deviation
• Now check that capturing is suspended
• As soon as the guiding deviation is below the threshold, first the suspended sequence will be restarted, but after receiving the next guiding frame (with still appropriate guiding deviation), the next sequence will be started, so that at least two sequences are marked with "Running"

With this change, this behavior is corrected so that recovery of a guiding deviation triggers only once a capture restart.