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

Trigger/TrigConfiguration/TrigConfIO/python/HLTTriggerConfigAccess.py

@@ -118,12 +118,12 @@ class HLTMonitoringAccess(TriggerConfigAccess):
     """
     this class provides access to the HLT monitoring json
     """
-    def __init__(self, filename = None, jsonString=None, dbalias = None, monikey = None ):
+    def __init__(self, filename = None, jsonString=None, dbalias = None, smkey = None ):
         """
         accessor needs to be initialized with either a filename or the dbalias and hlpskey
         """
         super(HLTMonitoringAccess,self).__init__( ConfigType.HLTMON, mainkey = "signatures",
-                                                  jsonString = jsonString, filename = filename, dbalias = dbalias, dbkey = monikey )
+                                                  jsonString = jsonString, filename = filename, dbalias = dbalias, dbkey = smkey )
 
         self.loader.setQuery({
             1: "SELECT HMG_DATA FROM( SELECT * FROM (SELECT SMT.SMT_HLT_MENU_ID FROM {schema}.SUPER_MASTER_TABLE SMT WHERE SMT.SMT_ID={dbkey}) lhs JOIN (SELECT HMG.HMG_HLT_MENU_ID,HMG.HMG_DATA FROM {schema}.HLT_MONITORING_GROUPS HMG WHERE HMG.HMG_IN_USE = 1) rhs ON lhs.SMT_HLT_MENU_ID = rhs.HMG_HLT_MENU_ID);" #for schema v7 (first implementation of monitoring groups)