In a nested job chain, max_order in super chain limits order for the whole nested chain

In a nested job chain If an outer job chain is configured with the attribute max_orders, inner job chains must not be configured with the attribute max_orders.
Configuration:
max_orders is only set for the outer job chain.

Use Case:
Exactly one biling cycle - i.e. a second billing cycle can only follow when the first cycle has been finished completely.

In a nested job chain, the attribute max_order limits the starts of orders in the combined job chain.

In order to work even when the super job chain is not yet configured,

• new orders must start in the first job chain.

Otherwise, the limit will not work.

All job chains must not have the attribute max_orders.

To reproduce the wrong behaviour in v1.7.3 please see the attached jobchain example.