[ATR-20700] Allow extra flexibility in HypoAlg RuntimeValidation for multi-leg chains
We are moving to support chains which change multiplicity mid-way through the processing.
An example is a multi-leg and/or multi-jet b-jet chain which is multiplicity [1] up to the jets, and then can change in bjet to multiplicity [1,1] or [2,1], or [5], etc.
For the multi-leg cases (e.g. [1,1], or [2,1] etc.), this means we start introducing per-leg DecisionIDs part way through the processing.
This MR modifies the logical-flow checking in the runtime trigger validation to allow the addition of chain-leg IDs, providing that the equivalent chain ID is present in all upstream Physics Objects.