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

ForwardDetectors/ForwardSimulation/ForwardRegionMgField/src/ForwardRegionFieldSvc.cxx

@@ -12,6 +12,7 @@
 
 #include "PathResolver/PathResolver.h"
 
+//comments kept as a reference
 // static ForwardRegionMgField q1("Q1",ForwardRegionField::Q1);
 // static ForwardRegionMgField q2("Q2",ForwardRegionField::Q2);
 // static ForwardRegionMgField q3("Q3",ForwardRegionField::Q3);
@@ -133,7 +134,7 @@ void MagField::ForwardRegionFieldSvc::getField(const double *xyz, double *bxyz,
 /** if deriv[9] is given, field derivatives are returned in kT/mm */
 void MagField::ForwardRegionFieldSvc::getFieldZR(const double*, double*, double*) const
 {
-  throw; //FIXME not supported yet.
+  throw std::logic_error("MagField::ForwardRegionFieldSvc::getFieldZR should not be called"); //FIXME not supported yet.
 }
 
 G4ThreeVector MagField::ForwardRegionFieldSvc::FieldValue(G4ThreeVector Point) const