Enforce gcc13 for LHAPDF too

[tvami]

Not a 100% how this happened (*) but on trunk the build failed:
https://github.com/LDMX-Software/dev-build-context/actions/runs/26589468131

(*) I think in the PR we prob still had a cached layer for the LHAPDF

In this PR now I enforce LHAPD uses gcc13 too

[tvami]

@tomeichlersmith do you have any other idea why this situation happened? If this is just what we have, I'd like to merge this w/o waiting 3 days and test it on v5.0.1

[tomeichlersmith]

I have no idea why it happened, but I'm fine with you making hot-fixes onto main.

I would just delete the old v6.0.0 release and make a new one. The build failing means that there isn't event a v6.0.0 tag on DockerHub for folks to pull from.

[tvami]

hey @tomeichlersmith I see this
https://github.com/LDMX-Software/dev-build-context/actions/runs/26649204120

The self-hosted runner lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.

is everything fine at UMN with the server?

[tvami]

I also see

Unable to extend expiry for GITHUB_TOKEN

not sure what that means

[tomeichlersmith]

The token is unrelated, it expires after 24hr and I don't believe that's a problem for us (I have seen it before).

UMN did have an internet outage on Wednesday which probably coincided with this error message. The runners appear to be back up https://github.com/organizations/LDMX-Software/settings/actions/runners but I can look at the physical machine when I'm back next week.

[tvami]

OK let's see if the main will trigger a new docker image as latest
https://github.com/LDMX-Software/dev-build-context/actions/runs/26899750394

but I think with this we lost the v6.0.0 tagged image