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

changed the description

This merge request affects 1 package:

• Trigger/TrigMonitoring/TrigJetMonitoring

This merge request affects 1 file:

• Trigger/TrigMonitoring/TrigJetMonitoring/python/TrigJetMonitorAlgorithm.py

Adding @jgeisen as watcher

added DQ JetEtmiss Trigger master review-pending-level-1 labels

CI Result SUCCESS (hash 9b4cb49c)

	Athena	AthSimulation	AthGeneration	AnalysisBase	AthAnalysis	DetCommon
externals
cmake
make
required tests
optional tests

Full details available on this CI monitor view
Athena: number of compilation errors 0, warnings 0
AthSimulation: number of compilation errors 0, warnings 0
AthGeneration: number of compilation errors 0, warnings 0
AnalysisBase: number of compilation errors 0, warnings 0
AthAnalysis: number of compilation errors 0, warnings 0
DetCommon: number of compilation errors 0, warnings 0
For experts only: Jenkins output [CI-MERGE-REQUEST-CC7 30979]

Code changes look fine, approving. Pienpen(L1)

added review-approved label and removed review-pending-level-1 label

merged

mentioned in commit 2d5365a6

added sweep:ignore label