Allow prioritization of lock usage

Current Situation

• Assume two job chains running in parallel.
  • Job Chain A: job_a1 -> job_a2
  • Job Chain B: job_b1 -> job_b2
• Assume
  • both jobs job_a1 and job_b1 to use an exclusive lock lock_a
  • both jobs job_a2 and job_b2 to use an exclusive lock lock_b
  • all jobs to use an exclusive lock lock_all
• If job chains A and B start then only one of the jobs job_a1 and job_b1 will run at the same time.
  • When job_a1 is completed then there is a choice if either the next node with job job_a2 in the same job chain A should be executed or if the first node with job job_b1 in job chain B should be executed .
• Currently users cannot specify the choice to be taken to either prioritize job nodes in the same job chain or to prioritize job nodes according to arrival of orders (which is the current behavior of JobScheduler Master).

Desired Behavior

• Users would like to configure the prioritization of lock usage when there is a choice to
  • either continue with the next node in the same job chain following the node that currently released a lock
  • or to continue with nodes across any job chains according to the sequence of arrival of orders with that nodes.