feat: update to actsv34.1.0

[osbornjd]

This updates us to Acts v34.1.0 from v30. We are still behind 4 major versions, but this gets us ~8 months of updates. Opening this now to start testing as much as we can before making a play build

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work for users)
• Requiring change in macros repository (Please provide links to the macros pull request in the last section)
• I am a member of GitHub organization of sPHENIX Collaboration, EIC, or ECCE (contact Chris Pinkenburg to join)

What kind of change does this PR introduce? (Bug fix, feature, ...)

TODOs (if applicable)

Links to other PRs in macros and calibration repositories (if applicable)

[sphenix-jenkins-ci]

Build & test report

Report for commit 02f86d12b084df39ac35c22a1980cea5ba4e7197:

• builds and tests overall are FAILURE.
• Build with configuration of alma9.2-gcc-14.2.0 / clang is FAILURE, 📊clang report (full)/(new), build log
• Build with configuration of alma9.2-gcc-14.2.0 / new is FAILURE, 📊Compiler report (full)/(new), build log
• Build with configuration of alma9.2-gcc-14.2.0 / scan is FAILURE, 📊scan-build report (full)/(new), build log
• Build with configuration of gcc-12.1.0 / new is FAILURE, 📊Compiler report (full)/(new), build log
• clang-tidy is SUCCESS, 📊clang-tidy report (full)/(new)
• cpp-check is FAILURE, 📊cppcheck report (full)/(new)

---

Automatically generated by sPHENIX Jenkins continuous integration
           

[osbornjd]

Here is a build with the Acts update
https://web.sdcc.bnl.gov/jenkins-sphenix/job/sPHENIX/job/Build-Master-gcc14/440/

[sphenix-jenkins-ci]

Build & test report

Report for commit 7f14170741ac000a91fa1d9f3e267c4891ddd947:

• builds and tests overall are FAILURE.

---

Automatically generated by sPHENIX Jenkins continuous integration
           

[sphenix-jenkins-ci]

Build & test report

Report for commit f38166904eaf7f5be83fb26746b3ada9e046e6be:

• builds and tests overall are FAILURE.
• Build with configuration of alma9.2-gcc-14.2.0 / clang is FAILURE, 📊clang report (full)/(new), build log
• Build with configuration of alma9.2-gcc-14.2.0 / new is FAILURE, 📊Compiler report (full)/(new), build log
• Build with configuration of alma9.2-gcc-14.2.0 / scan is FAILURE, 📊scan-build report (full)/(new), build log
• Build with configuration of gcc-12.1.0 / new is FAILURE, 📊Compiler report (full)/(new), build log
• clang-tidy is SUCCESS, 📊clang-tidy report (full)/(new)
• cpp-check is UNSTABLE, 📊cppcheck report (full)/(new)

---

Automatically generated by sPHENIX Jenkins continuous integration
           

[sphenix-jenkins-ci]

Build & test report

Report for commit 09660490f89881737b777ce4484eb59cc5aeff59:

• builds and tests overall are FAILURE.
• Build with configuration of alma9.2-gcc-14.2.0 / clang is FAILURE, 📊clang report (full)/(new), build log
• Build with configuration of alma9.2-gcc-14.2.0 / new is FAILURE, 📊Compiler report (full)/(new), build log
• Build with configuration of alma9.2-gcc-14.2.0 / scan is FAILURE, 📊scan-build report (full)/(new), build log
• Build with configuration of gcc-12.1.0 / new is FAILURE, 📊Compiler report (full)/(new), build log
• clang-tidy is SUCCESS, 📊clang-tidy report (full)/(new)
• cpp-check is SUCCESS, 📊cppcheck report (full)/(new)

---

Automatically generated by sPHENIX Jenkins continuous integration
           

[osbornjd]

Another build after more makefile fixing, for easy finding later
https://web.sdcc.bnl.gov/jenkins-sphenix/job/sPHENIX/job/Build-Master-gcc14/450/

[sphenix-jenkins-ci]

Build & test report

Report for commit f3bc4e11ee591bc9b10b5cc7415676a181507028:

• builds and tests overall are FAILURE.
• Build with configuration of alma9.2-gcc-14.2.0 / clang is FAILURE, 📊clang report (full)/(new), build log
• Build with configuration of alma9.2-gcc-14.2.0 / new is FAILURE, 📊Compiler report (full)/(new), build log
• Build with configuration of alma9.2-gcc-14.2.0 / scan is FAILURE, 📊scan-build report (full)/(new), build log
• Build with configuration of gcc-12.1.0 / new is FAILURE, 📊Compiler report (full)/(new), build log
• clang-tidy is SUCCESS, 📊clang-tidy report (full)/(new)
• cpp-check is SUCCESS, 📊cppcheck report (full)/(new)

---

Automatically generated by sPHENIX Jenkins continuous integration
           

[osbornjd]

Another try...
https://web.sdcc.bnl.gov/jenkins-sphenix/job/sPHENIX/job/Build-Master-gcc14/453/

[sphenix-jenkins-ci]

Build & test report

Report for commit f2e4b73452cd809821f7c94a369c956ef13c7ebc:

• builds and tests overall are FAILURE.
• Build with configuration of alma9.2-gcc-14.2.0 / clang is FAILURE, 📊clang report (full)/(new), build log
• Build with configuration of alma9.2-gcc-14.2.0 / new is FAILURE, 📊Compiler report (full)/(new), build log
• Build with configuration of alma9.2-gcc-14.2.0 / scan is FAILURE, 📊scan-build report (full)/(new), build log
• Build with configuration of gcc-12.1.0 / new is FAILURE, 📊Compiler report (full)/(new), build log
• clang-tidy is SUCCESS, 📊clang-tidy report (full)/(new)
• cpp-check is FAILURE, 📊cppcheck report (full)/(new)

---

Automatically generated by sPHENIX Jenkins continuous integration
           

[osbornjd]

Here is a successful build. QA is all consistent with p values of unity (!)

https://web.sdcc.bnl.gov/jenkins-sphenix/job/sPHENIX/job/Build-Master-gcc14/457/