Process change proposition: speed up Accepted of unreviewed new versions of developer MRs
Currently, when a developer proposes a MR, the bot sets the status to Accepted
after 72h of "inactivity" (no review).
If any new version of the MR is pushed, then the timer is reset, and the author has to wait 72h, again and again.
Note: Fast-Forward only versions should be ignored by the bot since 64a4895f.
The proposition is to reduce the wait period to 24h, only for subsequent version of the MRs, and not before 72h from the initial proposition time.
In other words, the bot would put the MR in Accepted
after the later of 24h after the last non-FF change and 72h after the MR creation time (if there is no review detected).