Fix release tagging

[frangio]

I don't want to forget about this, I believe with the 5.0.0 release we realized that #4646 hadn't fixed the issue where the wrong commit gets tagged as the one that was released. We manually fixed this for the past few releases. So far @ernestognw or I haven't been able to identify the error.

[ernestognw]

Happened again in 4.9.4 and 4.9.5 releases.

[frangio]

So 5.0.1 was ok?

[ernestognw]

Sorry, I meant 4.9.5 and 5.0.1. In the case of 4.9.4, it got released although the release job failed (not sure why it happened).

Common thing between both is that 4.9.4 and 4.9.5 ended up pointing 5.x. Note the 4.9.5 release job may be pushing the tags a step before, unless this message is normal:

[Amxx]

Happened in 5.1 and was un-noticed for a few days. Fixed that this morning.