More detailed validation of combinations in combined chains after HLT Navigation conversion

Adds code that check combinations returned by the matching tool in more details.

It was used to verify that navigation for combined chains are properly converted. I.e. the order is respected. The HLT_mu22_mu8noL1 chain was used in the test, about 10 passed events in the default test AOD.

But there is difference. This is because while converting Nav to Run3 format we assume all objects in RoI passed there is more valid combinations.

Trig::NavigationTesterAlg                            DEBUG Run 2 size 1
Trig::NavigationTesterAlg                            DEBUG {[type = 8, pt = 48835.1, eta = 0.287306, phi = -0.72485], [type = 8, pt = 49815, eta = 0.283152, phi = -0.721067]}
Trig::NavigationT...Trig::R3IParticleRetrievalTool   DEBUG Chain HLT_mu22_mu8noL1 passed
Trig::NavigationT...Trig::R3IParticleRetrievalTool   DEBUG Found 9 features
Trig::NavigationTesterAlg                            DEBUG Run 3 size 4
Trig::NavigationTesterAlg                            DEBUG {[type = 8, pt = 48835.1, eta = 0.287306, phi = -0.72485], [type = 8, pt = 49815, eta = 0.283152, phi = -0.721067]}
Trig::NavigationTesterAlg                            DEBUG {[type = 8, pt = 48835.1, eta = 0.287306, phi = -0.72485], [type = 8, pt = 36330.3, eta = 1.22412, phi = 2.48733]}
Trig::NavigationTesterAlg                            DEBUG {[type = 8, pt = 34891.9, eta = 1.22385, phi = 2.48921], [type = 8, pt = 49815, eta = 0.283152, phi = -0.721067]}
Trig::NavigationTesterAlg                            DEBUG {[type = 8, pt = 34891.9, eta = 1.22385, phi = 2.48921], [type = 8, pt = 36330.3, eta = 1.22412, phi = 2.48733]}

Can selection of objects in a single RoI in Run3 format still be done? I.e. highest pt. We could try doing it while converting but imo this is not the best place to take physics decisions.

Tagging @wprzygod @jburr @tamartin