Draft: [trigEGam] Integration beteween mongroups and TrigEgammaMonitoring

This MR is to include mongroups inside the TrigEgammaMonitoring framework.

• A method was implemented in the TrigEgammaMonitCategoryMT reading, for now, the mongoups from JSON local file produced by a ART test.
• At this moment, only the primary chains was configured, and then, called inside the TrigEgammaMonitorConfigMT.py file .
• In a next MR, we will include a logic to route chains to shifter and expert folders automatically, according to their respective mongroups.

JIRA Ticket: ATR-25841 .

ping: @safarzad , @cjmeyer , @fernando , @kyjones and @jlieberm

AtlasTest/CITest/test/RecoRun3Data.sh

@@ -4,4 +4,4 @@
 # Pilot beam collisions need a special export and preExec
 export TNS_ADMIN=/cvmfs/atlas.cern.ch/repo/sw/database/DBRelease/current/oracle-admin
 
-RunWorkflowTests_Run3.py -a q449 --CI -r -w DataReco -e '--maxEvents 500 --preExec "from AthenaConfiguration.AllConfigFlags import ConfigFlags; ConfigFlags.Trigger.triggerConfig = \"DB\"; DQMonFlags.useTrigger=False; DQMonFlags.doHLTMon=False;"' --threads 8 --no-output-checks
+RunWorkflowTests_Run3.py -a q449 --CI -r -w DataReco -e '--maxEvents 500 --skipEvents 60 --preExec "from AthenaConfiguration.AllConfigFlags import ConfigFlags; ConfigFlags.Trigger.triggerConfig = \"DB\"; DQMonFlags.useTrigger=False; DQMonFlags.doHLTMon=False;"' --threads 8 --no-output-checks