require >=1 jet trigger to be fired in MT JetMonitoring
This is a fix to the previously merged & reverted MR: !39772 (merged)
In the offline monitoring, we want to require at least any one jet trigger to have fired in an event before recording to not have a potential overlap with other signatures. So, adding a dedicated option to check for this, which calls the TDT with a regular expression.
The problem from last time (JetCleaningTool was called on jet collections without the necessary variables/decorations) is avoided this way.
Edited by Jannik Geisen