wrong merge request pipeline triggered

In a uprev_piglit_in_mesa job (it's from a verification pipeline of !52 (merged) merge request) a weird behavior has been observed:

Waiting for pipeline to be created for 79b595b3894ff7a01df5bd48066999259302ba8d https://gitlab.freedesktop.org/sergi/mesa/-/commit/79b595b3894ff7a01df5bd48066999259302ba8d
Pushed to existing merge request https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/21895
There isn't a previously in progress issue about this uprev to report this new uprev candidate.
Waiting for pipeline to be created for f47fe445cf26203668ff572a8578abf448fd52a6 https://gitlab.freedesktop.org/mesa/mesa/-/commit/f47fe445cf26203668ff572a8578abf448fd52a6
Waiting for pipeline to be ready https://gitlab.freedesktop.org/mesa/mesa/-/pipelines/834946

The tool amend the commit after the uprev pipeline, but after it pushes and reuses a previously created merge request, it starts looking for the pipeline of a previous contribution to this merge request. And it triggered the incorrect pipeline, one without the changes from the proposal it was doing.

---

Solution proposal: !54 (merged)