In a nested job chain, the attribute max_orders does not work in inner job chains

If an outer job chain has no attribute max_orders, then in each of the inner job chains the attribute max_orders can be set with different values.
Each inner job chains respects its individual value for max_orders for parallel orders.

Use Case:
A system which is able to support multiple clients where three billing cycles for three clients runs in parallel.
For one cycle there is a job chain which must be used from only one client in a moment

Original description:

In a nested job chain, it is not possible to combine job chains with different
When user configured nested jobchain with 4 sub jobchain

Main-JobChain
+-->Sub-JobChain1 ( max_order=1 )
+-->Sub-JobChain2 ( max_order=0 )
+-->Sub-JobChain3 ( max_order=1 )
+-->Sub-JobChain4 ( max_order=0 )

When multiple orders are submitted, expected behavior is, only single order should be executed in Sub-JobChain1, but multiple orders should be executed in parallel (since max_order=0) in the Sub-JobChain2, similarly in the Sub-JobChain3 and Sub-JobChain4

In attached example orders are waiting to be executed at Sub_JobChain1 and also run in parallel at Sub_JobChain2 , but at Sub_JobChain3 orders run in parallel , although due to max_order=1 , orders should be executed sequentially.

NOTE : all the nodes are set on_error suspend order

Please see the attached example to reproduce the bug