Set MC campaign centrally for MC trigger ART tests

While the correct MC campaign & settings were being used in TrigAnalysisTest transform-driven ART jobs running MC trigger simulation, the lack of preInclude support in runHLT.py meant that we were using the (bad) default settings for the LAr pileup simulation among other things, which was the source of ATR-28710.

To fix this in the many MC tests, this MR therefore:

1. Adds (pre/post)(Exec/Include) support to runHLT via TransformUtils -- postExec was already supported via bespoke code in !65198 (merged)
2. Adds a module providing template MC build & grid tests with just one place to commonly configure the global tag and MC campaign via flags & preInclude. These can be overridden cleanly (and only) through the MCExecStep constructor.
3. Adapt all TriggerTest MC jobs to use the common MCExecStep classes.

The HI, Cosmic, LowMu, and ITk tests use the MC campaign settings deemed most appropriate.

If we like this model, we could also do something similar for the test_trig_data jobs, but those do not have the same issue of the boilerplate conditions setup.

FYI @lbeemste @martindl

N.B. the HI Campaigns needed to ditch the doAlfaCtpin flag because this doesn't exist anymore (along with ALFA). Trigger simulation for ALFA, while needed for 2023, would be done in an older release.

added 3 commits

• 03d7e712 - Support pre/postInclude in runHLT
• 543c838f - Define a common MC execution step module for TriggerTest
• c52af73e - Move MC tests to use template step

Compare with previous version

added 3 commits

• d6507870 - Better support enabled signature lists in common MCExecStep
• ce6624da - Move all TriggerTest MC ART to MCBuild/GridStep to reduce boilerplate
• 4d5d5af5 - Adapt the slice reproduction ART

Compare with previous version

added 2 commits

• 36b2297a - Better support enabled signature lists in common MCExecStep
• 95670428 - Move all TriggerTest MC ART to MCBuild/GridStep to reduce boilerplate

Compare with previous version

I am a bit curious about a couple of inconsistencies in the various test configs:

1. Only the MC muon grid test sets ex.imf=False
2. A handful of HI and lowMu tests set Trigger.doRuntimeNaviVal=True. But specifically the lowMu build and grid tests do not set this consistently.

For now I have preserved the exact setup for all tests, apart from enabling the MC campaign (standard Run 3 except for the ITk tests where the corresponding Phase II campaign preInclude is set), and making the MC build test consistently use the same default global conditions tag as everything else.

Jenkins please retry a build

This merge request affects 3 packages:

• Trigger/TrigValidation/TrigValTools
• Trigger/TrigValidation/TriggerTest
• Trigger/TriggerCommon/TriggerJobOpts

Affected files list will not be printed in this case

Adding @fwinkl ,@okumura ,@fpastore ,@martindl ,@vmartin as watchers

added 24.0 Egamma ITk Trigger full-unit-tests labels

CI Result FAILURE (hash 95670428)

	Athena	AthAnalysis
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
AthAnalysis: number of compilation errors 0, warnings 0
For experts only: Jenkins output (remote access info)

added 1 commit

• a815da73 - Simple fixes

Compare with previous version

Jenkins please retry a build

This merge request affects 3 packages:

• Trigger/TrigValidation/TrigValTools
• Trigger/TrigValidation/TriggerTest
• Trigger/TriggerCommon/TriggerJobOpts

Affected files list will not be printed in this case

Adding @vmartin ,@martindl ,@fwinkl ,@okumura ,@fpastore as watchers

CI Result FAILURE (hash a815da73)

	Athena	AthAnalysis
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 1
AthAnalysis: number of compilation errors 0, warnings 0
For experts only: Jenkins output (remote access info)

added 1 commit

• 5196f839 - Correct import

Compare with previous version

added 1 commit

• e8d0a64c - Switch to dedicated MC conditions for HI and low mu

Compare with previous version

added 3 commits

• f2a08f99 - Switch to dedicated MC conditions for HI and low mu
• d22917ba - Remove obsolete flag from HI campaign settings in 24.0
• 91199e65 - Update DevHI MC build ref

Compare with previous version

Jenkins please retry a build

This merge request affects 4 packages:

• Tools/Campaigns
• Trigger/TrigValidation/TrigValTools
• Trigger/TrigValidation/TriggerTest
• Trigger/TriggerCommon/TriggerJobOpts

Affected files list will not be printed in this case

Adding @vmartin ,@fpastore ,@okumura ,@fwinkl ,@martindl as watchers

added Tools analysis-review-required changes-trigger-counts labels

@jchapman FYI, removed the obsolete flag from MC23 HI config function as discussed. Seems better to activate this for the HI tests even if not finalised, such that when it is, it is reflected in our ART.

Note: Cosmics didn't have any dedicated Campaign setup so just gets default. I am a bit sceptical that mu=60 for low-mu is reflective of detector settings, but would settle for using that configuration in our tests and leaving it to others to determine what the correct settings ought to be.

It would probably be better to use the MC23a/d/e/gNoPileUp setup for cosmics; what do you think?