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/TrigEvent/TrigCombinedEvent/src/TrigComposite.cxx

 /*
-  Copyright (C) 2002-2021 CERN for the benefit of the ATLAS collaboration
+  Copyright (C) 2002-2022 CERN for the benefit of the ATLAS collaboration
 */
 
 //#include <iostream>
@@ -137,6 +137,7 @@ std::map<std::string, T>& TrigComposite::detailsMap() {
   [[maybe_unused]]
   int z =
     sizeof(struct TrigComposite_does_not_support_that_type_as_a_detail);
+  std::abort();
 }
 
 template<typename T>
@@ -145,7 +146,7 @@ const std::map<std::string, T>& TrigComposite::detailsMap() const {
   [[maybe_unused]]
   int z =
     sizeof(struct TrigComposite_does_not_support_that_type_as_a_detail);
-
+  std::abort();
 }
 
 // this macro helps instantiating methods for all necessary template arguments