Adding option to EventDefinitionM26 to directly add the trigger ts information to the event
Since we have observed a mismatch between the pivot frame-based definition of events and using single trigger events a parameter to add the trigger information directly in the module EventDefinitionM26 is introduced. If the option is selected an event with a duration of 3 frames (-1/+2 frames around the trigger ts) is defined. Compared to using the EventLoaderEUDAQ2 for TLU data, this leads to a significant increase in the statistics available (363732->614096 for the data set I've used, see residuals). No significant change in the overall efficiency is observed, see plots attached to MR