Factor out tracking, update all CIs to full sequence

[tvami]

I am updating ldmx-sw, here are the details.

What are the issues that this addresses?

This resolves #1549

Check List

• I successfully compiled ldmx-sw with my developments
• I ran my developments and the following shows that they are successful.

I tested with the ecal PN sample.

I did two things in this PR

1. update the CIs to use the latest tracking, for this I made a new file so I dont have to copy a lot of things, I also updated reco.py @bloodyyugo I took the numbers from Add ambiguity resolution to tracking #1526 (and rounded them).

2. Ecal Veto now relies on the tracking for the photon projection, when it can (i.e. if a recoil track exists). With this we also introduced another ep angle as measured at the target, or as it used to be measured at the ECAL face. Much of this work was done by @JYoo001

[tvami]

Maybe I should have done this in two steps...

But let's concentrate on the tracking changes first:
[the followings are for the kaon sample, for the recoil DQM variables]

1. I dont understand the dip in the middle of this distribution:

2. Recoil layer hits are gone??

3. The match nHits change I could expect from the ambiguity resolution

4. Number of tracks has a big jump at the zero bin

5. NDF got higher

6. Sigma p vs p got better

7. But the pull is worse

8. I must have missed a setting for the target projection, bc the histograms are empty, I'll check this asap

9. More duplicates

[Now moving to the tagger]

10. Wow the tagger d0 is shifted a lot, is that real or did I mistype some number??

11. All the duplicates plots are empty for the tagger

12. Same for layer hits and matched layer hits

13. Num of tracks in the tagger looks good tho!

14. NDF is all at 10 now

15. Together with the number of hits, that's all at 14 now

16. The pT might be just because we get the track in an ange?

17. The "pZ" looks good

18. Pull d0 is gone, as is the phi d0

19. The z0 got much wider

20. Note to self: I forgot to add tracking to the signal CI

@EBerzin @bloodyyugo are these changes according to your expectations?

[tvami]

The validation workflow is running here: https://github.com/LDMX-Software/ldmx-sw/actions/runs/13081772275.

OK so in this I kept the CKF the usual DQM, and introduced new ones for the GSF. Things pass the K-S test... This is a bit surprising to be since I changed to the digis + changed the variables. But if it's true that means everything in my prev comment comes from the combination of the ambiguity resolution and the GSF

[tvami]

Things pass the K-S test... This is a bit surprising to be since I changed to the digis + changed the variables

Ignore all the workflows that got triggered by my command line testing, it doesnt check out the correct branch. Now I triggered test with the usual "go to draft, ready for review" way

[tvami]

Well this has not much to do with this PR's developments, but I guess it got revealed it now:

[ ecalVeto ] 122  info:  Recoil tracking for projections; with 1 tracks, fiducial in tracker = true
  [ ecalVeto ] 122  info: Finding linreg tracks from a total of 6 hits using a radius of 35 mm
  [ ecalVeto ] 122  info:  MIP tracking completed; found 0 straight tracks and 0 lin-reg tracks
  [ ecalVeto ] 122  info:   BDT was ran, score is 0.999697
  [ hcalVeto ] 122  info: There are 0 / 0 HCal hits read out. 0 are not associated with the recoil ele. Total PE of 0
  [ hcalVeto ] 122  info: HCAL veto passed? true
  [ ElectronCounter ] 122  info: Found 1 electrons (tracks) using input collection TriggerPadTracksY_
  [ trigger ] 122  info: Got trigger energy cut 3000 for 1 electrons counted in the event.
  [ trigger ] 122  info: Got trigger energy sum 807.849; and decision is pass = true
  05:29:18    PROP           ERROR     Step failed with MagneticFieldError:1: Interpolation out of bounds was requested
  
   *** Break *** segmentation violation

[tvami]

I will delay adding the tracking to the signal, and made an issue about it: #1562

[tvami]

/run-validation

[github-actions]

The validation workflow is running here: https://github.com/LDMX-Software/ldmx-sw/actions/runs/13140200480.

[tvami]

/run-validation

[github-actions]

The validation workflow is running here: https://github.com/LDMX-Software/ldmx-sw/actions/runs/13188891225.

[tvami]

Validation with the version where the min num hit is back to 6:
https://github.com/LDMX-Software/ldmx-sw/actions/runs/13233604311/job/36934626779?pr=1551

[tvami]

I will close this PR and have the content done in pieces