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

PhysicsAnalysis/DerivationFramework/DerivationFrameworkTrigger/src/TriggerMatchingTool.cxx

@@ -213,7 +213,7 @@ namespace DerivationFramework {
           // index. Otherwise we have to locate the correct proxy from the element
           if (container->trackIndices())
             links.emplace_back(
-                m_offlineInputs.at(part->type()).hashedKey(),
+                m_offlineInputs.at(part->type()).key(),
                 part->index(),
                 extendedCtx.proxy());
           else