feat: support Acts versions from v31 up to v36 (to be released)

[wdconinc]

Briefly, what does this PR introduce?

This adapts our tracking algorithms to any Acts version between v31 and v36 (to be released, so additional refactors may hit the Acts main branch that would need porting).

The commits in this branch are topologically ordered with reference to the commit message title, Acts PR number, and version validity. All commits compile individually, but no event-for-event validation has been performed.

The support for mulitple versions is done by somewhat extensive use of preprocessor directives based on Acts_VERSION_MAJOR.

Builds with:

• v32.1.0: https://eicweb.phy.anl.gov/containers/eic_container/-/jobs/3481513#L3103
• v33.1.0: https://eicweb.phy.anl.gov/containers/eic_container/-/jobs/3482111#L3549
• v34.1.0: https://eicweb.phy.anl.gov/containers/eic_container/-/jobs/3482134#L3699
• v35.0.0: locally, but not yet in eic_container since this requires #1520 and related eic-spack PRs first

What kind of change does this PR introduce?

• [ ] Bug fix (issue #__)
• [x] New feature (issue: Acts versions are released faster than we can keep up with)
• [ ] Documentation update
• [ ] Other: __

Please check if this PR fulfills the following:

• [ ] Tests for the changes have been added
• [ ] Documentation has been added / updated
• [ ] Changes have been communicated to collaborators

Does this PR introduce breaking changes? What changes might users need to make to their code?

No.

Does this PR change default behavior?

No.

[github-actions[bot]]

Capybara summary for PR 1525

• rec_dis_10x100_minQ2=0_craterlake
• rec_dis_10x100_minQ2=1000_craterlake_tracking_only
• rec_dis_18x275_minQ2=0_craterlake
• rec_dis_18x275_minQ2=1000_craterlake
• rec_dis_5x41_minQ2=0_craterlake
• rec_e_1GeV_20GeV_craterlake
• rec_pi_1GeV_20GeV_craterlake ^{_{Last updated 2024-07-03T15:58-04:00 c8580130b8607a4272afce9d93534d6c63872571}}

[wdconinc]

The (short term) scope for merging here is:

• compiles and no changes for Acts-31 (capybara reports),
• compiles for Acts-32 through Acts-35 (eicweb pipelines).

The next steps are:

• upgrading versions of Acts on eicweb, based on validation in benchmarks.

Out of scope for this PR are:

• issues that may be found later during validation; those will be fixed as they are found, in individual PRs.

This enables the possibility for validation from the actual validation, and hopefully leads to a faster workflow in the long run.

[wdconinc]

Two mistakes corrected and force pushed.

Both of the following ifs should apply for Acts_VERSION_MAJOR >= 33, not 32.

• https://github.com/eic/EICrecon/pull/1525/commits/cdcf3d219eb97096a8058441bc593c42369566c3#diff-d7fb27b053533c960f76460cd41ed5af010d6ab2c19aecb233216a29b3a01c2bR96
• https://github.com/eic/EICrecon/pull/1525/commits/cdcf3d219eb97096a8058441bc593c42369566c3#diff-d7fb27b053533c960f76460cd41ed5af010d6ab2c19aecb233216a29b3a01c2bR108

[sonarcloud[bot]]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[wdconinc]

No major diffs (but many minor diffs): https://wdconinc.github.io/capybara-reports/1c667510d01aed2d228e74ea6e574252/