chore: acts 45.1.1

[wdconinc]

Briefly, what does this PR introduce?

Needs:

• chore: eic-spack: convert repository to spack packages API v2 repo layout #174
• chore: dd4hep-1.35 (rntuple support) #149
• juggler: don't require acts +tgeo for newer juggler eic-spack#838
• k4actstracking: don't depend on acts +tgeo key4hep/key4hep-spack#861

This PR update acts to v45.1.1. Follows #166 with correct branch name. Juggler gets a minor upgrade to make sure it can handle the updated interfaces in Acts v45.

[Copilot]

Pull request overview

This PR updates the EIC container Spack environment to use Acts v45.1.1, aligning the pinned Acts version with the upstream Spack package definition updates referenced in #166.

Changes:

• Add upstream spack/spack-packages cherry-picks needed to introduce Acts v45.x versions and improved variant dependency handling.
• Update spack-environment/packages.yaml to require acts@45.1.1 (keeping the existing variant set).

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
spack-packages.sh	Adds the upstream cherry-pick commits that introduce Acts v45.0.0 / v45.1.0 / v45.1.1 and variant dependency handling updates.
spack-environment/packages.yaml	Pins Acts from @44.4.0 to @45.1.1 under package requirements.

[veprbl]

Physics benchmarks are unhappy:

[] [acts] [error] invalid det_element!!! det_element == nullptr 

[wdconinc]

Yeah. Fixed in then Gen1/Gen3 geometry branch... Need to extract and apply cleanly.

[wdconinc]

Yeah. Fixed in then Gen1/Gen3 geometry branch... Need to extract and apply cleanly.

Actually, this is already fixed (eic/EICrecon#2466). It just doesn't retroactively appear in the latest released EICrecon that's used in the default workflow (and nightly succeeded). So this is effectively on hold until the next release.

[Copilot]

Pull request overview

Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.

[wdconinc]

Looks good in https://eicweb.phy.anl.gov/EIC/benchmarks/detector_benchmarks/-/jobs/7393001/artifacts/file/results/tracking_performances_dis/epic_craterlake_tracking_only/pythia8NCDIS_18x275_minQ2=1_combined_5/plots.pdf (nightly).

[veprbl]

I see some minor discrepancies in track projections
https://veprbl.github.io/capybara-reports/56eba532508bf97a9f7927efa94f5478/

Looks like it picks up additional projection points in fEMCal and LFHCAL.

That are in forward, as expected

But there is a bit of phi modulation to it?

The predicted time of 25 meters is a bit concerning, is that a loop in the propagation?