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

Build/AtlasBuildScripts/build_project_externals.sh

@@ -182,7 +182,9 @@ if [ ${ERROR_COUNT} -ne 0 ]; then
     if [ "${ATLAS_CI_BUILD}" = "1" ]; then
         echo "Removing external project artifacts..."
         rm -rf "${ATLAS_BUILD_DIR}/build/${ATLAS_EXT_PROJECT_NAME}/src"
+        rm -rf "${ATLAS_BUILD_DIR}/build/${ATLAS_EXT_PROJECT_NAME}/tmp"
         rm -rf "${ATLAS_BUILD_DIR}/build/${ATLAS_EXT_PROJECT_NAME}/External"
+        rm -rf "${ATLAS_BUILD_DIR}/build/${ATLAS_EXT_PROJECT_NAME}/${BINARY_TAG}"
     fi
 else
     cp "${ATLAS_PROJECT_DIR}/externals.txt" "${externals_stamp}"