Remove requirement for events to trigger jet chain in JetMonitoring

This MR is to address & fix an unforeseen problem observed in https://its.cern.ch/jira/browse/ATR-23048 which seems to be caused by requiring events in the JetMonitoring to fire at least one jet chain.

We are not removing this feature or functionality, but simply not require it in the online JetMonitoring config, as it is turned off by default

Tagging @valentem @jbossios

Trigger/TrigMonitoring/TrigJetMonitoring/python/TrigJetMonitorAlgorithm.py

@@ -276,7 +276,7 @@ def basicJetMonAlgSpec(jetcoll,isOnline,athenaMT):
   jetcollFolder = jetcoll
   if jetcoll in JetCollRemapping.JetCollRun2ToRun3 and not athenaMT:
     jetcollFolder = JetCollRemapping.JetCollRun2ToRun3[jetcoll]
-  Conf = JetMonAlgSpec(jetcoll+"Mon",JetContainerName = jetcoll, defaultPath = path, eventFiresAnyJetChain=isOnline, topLevelDir=TopLevelDir, bottomLevelDir=jetcollFolder, failureOnMissingContainer=False)
+  Conf = JetMonAlgSpec(jetcoll+"Mon",JetContainerName = jetcoll, defaultPath = path, topLevelDir=TopLevelDir, bottomLevelDir=jetcollFolder, failureOnMissingContainer=False)
 
   # Now start filling the histo spec list    
   Conf.appendHistos(