fix for medium1 tracktwo/track tau trigger combinations
Issue was caused by calling TrigEFTauMVHypoTool
twice : once at Preselection and another time at Precision step.
Bug : for "medium1", TrigEFTauMVHypoTool is trying to cut on the BDT score which is not calculated at Preselection level, but it's calculated only at Precision level -> Hypo was cutting on null quantity
Solution : bypass the cut on BDT score for the first TrigEFTauMVHypoTool
instance and let the cut be applied only during the second instance at Precision level
References updated -> expect count increase for "medium1_tracktwo" and "medium1_track" combinations
Hope to not pickup MR conflicts with !43405 (merged)
Edited by Antonio De Maria