Release workflow creates `latest` tag on previous version minor releases

[elena-kolevska]

This run added a latest tag on a 4.30.0 release, while we already have a 5.6.0 version out.

Expected behaviour:
A latest tag is only added if there aren't any higher versions published (as defined by SemVer)

[nkaradzhov]

#1977 provides solution for the v4 branch. Any other existing major release branch will have to be fixed as well.
Turns out the semantic-release package supports maintenance branches out of the box.
I propose we adopt this approach in the main branch. Benefits will be that any further major releases will work out of the box if we use semantic-release's branch naming convention ( for example 8.x, 9.x, etc ). The change will still have to be cherry-picked in all the previously created releases in order to work for them

@htemelski @elena-kolevska what do you think?