Add 4D reconstruction options and support for U2 ‘emulation’ settings

Requires Moore!4715 (merged)

FYI @seaso

Adds a number of new tests that will appear under qmtest/Reco.qms/ that exercise various configurations of the tracking + RICH reconstruction

• track_rich_reco_2024_data.qmt - Regular reconstruction on real 2024 data
• track_rich_reco_2024_MC.qmt - Regular reconstruction on 2024 MC
• track_rich_reco_2024_MC_4D_EmulateRawFromMC_MCTracks.qmt - Enables 4D reco with 2024 MC, where the RICH Raw data is emulated from MCHits and the tracks are also created from MC information.
• track_rich_reco_2024_MC_4D_EmulateRawFromMC.qmt - Enables 4D reco with 2024 MC, where the RICH Raw data is emulated from MCHits but the regular run 3 tracking is used. In this case, to support the needs for 4D reco a track time origin is inserted into each track, after the fact, using MC PV origin time. In all other regard though the tracks a regular uncheated run3 tracks.
• track_rich_reco_2024_MC_4D.qmt - Like track_rich_reco_2024_MC_4D_EmulateRawFromMC.qmt but the regular rich decoding is also used. To support 4D timestamps from MChits are inserted into the decoded data after the fact.
• track_rich_reco_2024_MC_4D_EmulateRawFromMC_MCTracks_PixelPosFromMC_PhotonsUseMC.qmt - Like track_rich_reco_2024_MC_4D_EmulateRawFromMC_MCTracks.qmt but uses MC information to cheat the pixel quantisation (sizes) and expected CK theta resolutions.

In addition, the following tests run specific tunings for the Upgrade 2 scoping document scenario 1 and 2 settings

• track_rich_reco_2024_MC_U2Emulation_scenario1.qmt
• track_rich_reco_2024_MC_U2Emulation_scenario2.qmt