Incomprehensible error message when an order is started and all job chain nodes are skipped

Current Situation

• Example job chain /xxx:

  <job_chain orders_recoverable="yes"  visible="yes">
      <job_chain_node state="start"
                      job="first_job"
                      next_state="SUCCESS"
                      error_state="ERROR"/>
      <job_chain_node state="SUCCESS"/>
      <job_chain_node state="ERROR"/>
  </job_chain>
  

• If an order is started and the first job chain node is skipped, e.g. via the command <job_chain_node.modify action="next_state" job_chain="/xxx" state="start"/>) then the following message is logged and an error is raised:

  SCHEDULER-859  Due to action='next_state' the state 'start' has been skipped. Next state is 'SUCCESS'
  ...
  [ERROR SCHEDULER-149  There is no job in job chain "/xxx" for the state "SUCCESS"]
  

Unchanged Behavior

• This behavior remains unchanged and applies to
  • the first job node in the job chain if it is the only node. This is due to the fact that without any active (not skipped) job nodes an order cannot be processed by the job chain.
  • any range of job nodes that an order is configured to be executed for and all of these job nodes are in a skipped state.
• The following behavior is changed: disappearance and appearance of orders in job chains with skipped/unskipped job nodes, see JS-864