jet hypo - use Pt rather than Et as a threshold variable.
For the simple variable, the et thresholds have been switched variable has been switched from et to pt.
For the dijet scenario, either 'et' or 'pt' may appear in the scenario string.
The HT scenario has not been changed. This will be changed once othercurrently ongoing work has been completed.
The fbdj scenarios remain with et cuts. pt cuts may be enabled later.
Small differences in the chain counts were observed.
Add support for pt cuts: TrigHLTJetHypo/python/ConditionDefaults.py python/FastReductionAlgToolFactory.py TrigHLTJetHypo/src/PtConditionMT.cxx, h TrigHLTJetHypo/src/TrigJetConditionConfig_pt.cxx, h TrigHLTJetHypo/src/components/TrigHLTJetHypo_entries.cxx
allow pt cuts for the dijet scenario: TrigHLTJetHypo/python/scenario_dijet.py
witch to using pt as a threshold variable for the simple scenario: TrigHLTJetHypo/python/scenario_simple.py
update menu items: HLTMenuConfig/python/HLTMenuConfig/Menu/LS2_v1.py HLTMenuConfig/Menu/SignatureDicts.py
update Trigger Art reference files: TrigAnalysisTest/share/ref_RDOtoRDOTrig_v1Dev_build.ref TriggerTest/share/ref_data_v1Dev_build.ref