Fix decreasing time trend of loopers in last event

[jackal1-66]

Current implementation replaces average time interval of the last event with a wider one considering as boundary the start of the second orbit after the last interaction record. A single orbit was not enough, leading to similar results to the previous implementation, while this creates a much sharper decrease as shown in the attached plot.

Previous results are shown in this WP12 presentation.
This development has been tested here

[github-actions]

REQUEST FOR PRODUCTION RELEASES:
To request your PR to be included in production software, please add the corresponding labels called "async-" to your PR. Add the labels directly (if you have the permissions) or add a comment of the form (note that labels are separated by a ",")

+async-label <label1>, <label2>, !<label3> ...

This will add <label1> and <label2> and removes <label3>.

The following labels are available
async-2023-pbpb-apass4
async-2023-pp-apass4
async-2024-pp-apass1
async-2022-pp-apass7
async-2024-pp-cpass0
async-2024-PbPb-apass1
async-2024-ppRef-apass1
async-2024-PbPb-apass2
async-2023-PbPb-apass5

[jackal1-66]

As for the previous PR, the CI fails because of missing collision context. It works when running on normal workflows. Merging