Adding skeleton of L0Muon TGC simulation

As with !77881 (merged), a first version of the stage-1 simulation algorithm for the L0 muon endcap trigger, based on TGC, is added.

The package includes the skeleton of an algorithm, to be completed with the actual implementation.

Tagging: @rosati

This merge request affects 1 package:

• Trigger/TrigT1/Muon/L0MuonS1TGC

This merge request affects 5 files:

• Trigger/TrigT1/Muon/L0MuonS1TGC/CMakeLists.txt
• Trigger/TrigT1/Muon/L0MuonS1TGC/python/L0MuonS1TGCConfig.py
• Trigger/TrigT1/Muon/L0MuonS1TGC/src/L0MuonTGCSim.cxx
• Trigger/TrigT1/Muon/L0MuonS1TGC/src/L0MuonTGCSim.h
• Trigger/TrigT1/Muon/L0MuonS1TGC/src/components/L0MuonS1TGC_entries.cxx

Adding @junpei as watcher

added Trigger main review-pending-level-1 labels

CI Result SUCCESS (hash 9d1d584b)

	Athena
externals
cmake
make
tests

Full details available on this CI monitor view. Check the JIRA CI status board for known problems
Athena: number of compilation errors 0, warnings 0
For experts only: Jenkins output (remote access info)

added 1 commit

• a3fcc612 - applied suggested improvements

Compare with previous version

Jenkins please retry a build

This merge request affects 1 package:

• Trigger/TrigT1/Muon/L0MuonS1TGC

This merge request affects 5 files:

• Trigger/TrigT1/Muon/L0MuonS1TGC/CMakeLists.txt
• Trigger/TrigT1/Muon/L0MuonS1TGC/python/L0MuonS1TGCConfig.py
• Trigger/TrigT1/Muon/L0MuonS1TGC/src/L0MuonTGCSim.cxx
• Trigger/TrigT1/Muon/L0MuonS1TGC/src/L0MuonTGCSim.h
• Trigger/TrigT1/Muon/L0MuonS1TGC/src/components/L0MuonS1TGC_entries.cxx

Adding @junpei as watcher

There were multiple CI triggers for this MR and commit. The system ignored duplicates but the GitLab pipeline status may incorrectly show the job as failed. Once the remaining job finished running, the CI results will be posted as usual.

Why are we creating separate packages for all these muon technologies. Can we just have all this in one L0Muon simulation package?