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

Tracking/TrkG4Components/TrkG4UserActions/TrkG4UserActions/MaterialStepRecorder.h

 /*
-  Copyright (C) 2002-2019 CERN for the benefit of the ATLAS collaboration
+  Copyright (C) 2002-2022 CERN for the benefit of the ATLAS collaboration
 */
 
 ///////////////////////////////////////////////////////////////////
@@ -47,11 +47,8 @@ namespace G4UA
     virtual void UserSteppingAction(const G4Step*) override;
   private:
 
-    typedef ServiceHandle<StoreGateSvc> StoreGateSvc_t;
     /// Pointer to StoreGate (event store by default)
-    mutable StoreGateSvc_t m_evtStore;
-    /// Pointer to StoreGate (detector store by default)
-    mutable StoreGateSvc_t m_detStore;
+    ServiceHandle<StoreGateSvc> m_evtStore;
 
     Trk::MaterialStepCollection*    m_matStepCollection; //FIXME convert to a WriteHandle
     std::string                     m_matStepCollectionName; //FIXME should be passed in via a Config struct rather than hardcoded.