RD Baryonic line: Add Xi0b2Xi0LL line

• is "[Xi0 -> Lambda0 pi0]cc" correct? see here -> thanks @vlisovsk, yes it is because of baryon number conservation
• Should we include lambda LD on top of LL and DD, this was done for Run 2? -> for now not, (almost) no use in Run 2 analysis
• In Run 3 lambda DD and LL differ only in mass_window_comb (LL: 50 MeV, DD: 80 MeV) and mass_window (LL: 35 MeV, DD: 64 MeV), the first is related to mass of Lambda for CombinationCut, the later for CompositeCut -> a bit different now, but follow along new RD lambda objects
• All cuts from Run 2 need to be cross checked with the new implementation -> more or less done, some more detailed tests to come

Discussion 28.01.25:

• problem: general missing person power and interested analysts for Run 3 analysis
• one day hackathon on 11.02. with @lcalefic @jherdiec
• next steps:
  • rd_resolved_pi0s objects not yet used except for this analysis, look at other group's setup of resolved pi0s and ask them if problems arise
  • aim to have first a running version (with DD as these are dominant contribution of track types in Run2 analysis) that we are able to run over existing block 1/2 data
  • request additional small simulation samples for expected nominal 2025 conditions, e.g. 100k per mode
  • once this works, we can add it for LL, maybe for LD (as said in Run2 no large contribution from these), need to check how vertex of combined LD line would work in Run 3 compared to Run2, e.g. in CPV lines
  • then we can tune it in more detail on efficiencies and bandwith

Tests

Time taken:

rd-devel-march25:
time: 2:10:13.16 total, compression: 44.74%, 294 KiB => 131 KiB

Xi0b2Xi0MuMu:
time: 2:31:54.97 total, compression: 37.93%, 581 KiB => 220 KiB

Rates of this MR comparing against rd-devel-march25 with data (100_000 events):

	rate (before)	rate (after)	difference	difference (%)
Hlt2RD_LbToPpKmPipPimEE	38.6908	38.6908	0	0
Hlt2RD_Xib0ToXi0MuMu_DD	nan	38.6908	nan	nan
Hlt2RD_LbToPpPimEE	25.7938	25.7938	0	0
Hlt2RD_LbToL0PipPimEE_LL	25.7938	25.7938	0	0
Hlt2RD_Xib0ToXi0MuMu_LL	nan	25.7938	nan	nan
Hlt2RD_LbToL0PipPimEE_DD	12.8969	12.8969	0	0
Hlt2RD_LbToPpKS0PimEE_LL	12.8969	12.8969	0	0
Hlt2RD_LbToPpKS0PimEE_DD	12.8969	12.8969	0	0
Hlt2RD_XibmToXimEE_LLL	nan	0	nan	nan
Hlt2RD_XibmToXimEE_DDL	0	0	0	nan
Hlt2RD_OmegabmToXimEE_DDD	0	0	0	nan
Hlt2RD_XibmToXimEE_DDD	0	0	0	nan
Hlt2RD_XibmToXimMuMu_DDD	0	0	0	nan
Hlt2RD_OmegabmToXimMuMu_LLL	0	0	0	nan
Hlt2RD_OmegabmToXimMuMu_DDL	0	0	0	nan
Hlt2RD_XibmToXimMuMu_DDL	0	0	0	nan
Hlt2RD_OmegabmToXimMuMu_DDD	0	0	0	nan
Hlt2RD_OmegabmToOmegamMuMu_DDD	0	0	0	nan
Hlt2RD_OmegabmToOmegamMuMu_LLL	0	0	0	nan
Hlt2RD_OmegabmToOmegamMuMu_DDL	0	0	0	nan
Hlt2RD_OmegabmToOmegamEE_LLL	0	0	0	nan
Hlt2RD_OmegabmToOmegamEE_DDL	0	0	0	nan
Hlt2RD_OmegabmToOmegamEE_DDD	0	0	0	nan
Hlt2RD_LbToPpPimMuMu	0	0	0	nan
Hlt2RD_LbToPpKmPipPimMuMu	0	0	0	nan
Hlt2RD_LbToPpKS0PimMuMu_LL	0	0	0	nan
Hlt2RD_LbToPpKS0PimMuMu_DD	0	0	0	nan
Hlt2RD_LbToL0PipPimMuMu_LL	0	0	0	nan
Hlt2RD_LbToL0PipPimMuMu_DD	0	0	0	nan
Hlt2RD_XibmToXimMuMu_LLL	0	0	0	nan