Schedule decoding of phase-1 MUCTPI DAQ ROB in offline reconstruction
The xAOD::MuonRoIContainer#LVL1MuonRoIs in the Run-3 path is produced during the HLT, then serialised and saved to ByteStream. Offline reconstruction decodes it from ByteStream with all the rest of HLT containers and saves to ESD/AOD. This container is produced during HLT by decoding the MUCTPI data which arrived via the RoIBuilder ROB. There is no need to decode these data again in offline reconstruction, because we just read what HLT read online.
However, in ATR-23992 a wish was expressed to decode the MUCTPI DAQ ROB data during offline reconstruction. This change is implemented here. The same tool is used as online, but the input is the DAQ ROB and the output container is named LVL1MuonRoIsDAQ. It is also configured to be saved to ESD/AOD, so in the end we will have both LVL1MuonRoIs and LVL1MuonRoIsDAQ in the AOD.
Note: This is mostly useful for the reconstruction of actual data straight from P1. In the HLT Reprocessing workflow, the MUCTPI RoIB ROB is overwritten during HLT rerunning with a simulated output, but the DAQ ROB is not and still contains the original data from the original run at P1. Therefore in HLT Reprocessing output these two ROBs correspond to different MUCTPI decisions.