Reassigning orders when unskipping the first job in a workflow

Current Situation

• An order that is added to a workflow considers if the fist job is skipped:
  • If the first job is skipped then the order internally moves to the next job or other instruction and waits for its start time.
  • If the job is unskipped later on then the order remains with the position of the job or instruction that it was assigned when originally skipping the first job.
• The technical reason being that orders are started by Agents, not by the Controller. Therefore, the Controller attaches the order to the Agent that is assigned the first job to be executed. This has to be decided at the point in time of order submission as users want to submit orders (for days) in advance. In addition, users want orders to start independently of a Controller's availability. It would be wrong to decide about the Agent to start an order (for whatever job will be the first to be executed) at the point in time of order start. Agents are autonomous, this is highly important for resilience.
• This explains why the behavior for later jobs in a workflow is different: as the order does not move to later jobs before starting. Users can skip and unskip later jobs at their will as long as the order is not started.
• Admittedly users who are unaware of the resilience implications might find it confusing that unskipping the first job in a workflow behaves differently from unskipping later jobs.

Desired Behavior

• The unskip operation in the GUI should consider the situation: if the first job in a workflow is unskipped then the API will
  • revoke any scheduled orders for the workflow.
  • re-submit any scheduled orders to cause them being attached the Agent that is assigned the now first job to be executed in the workflow.
• Order IDs will not change, nor will the scheduled time change. The behavior is similar to applying the "cancel" operation in the Daily Plan view (that moves orders to the planned state) and then to "submit" planned orders.

Maintainer Note
If an Agent to which the orders are attached is not coupled, then no reassigment is performed.