Revert "Merge branch 'sort-git-tags-node-semver' into 'master'"

What does this MR do?

!319 (merged) caused a regression in the release jobs. The leading v is removed because semver normalises the versions. As a result, the job fails when comparing the version returned by semver with the one found in the CHANGELOG.

semver -l v3.0.0
3.0.0

What are the relevant issue numbers?

None

Does this MR meet the acceptance criteria?

• Tests added for this feature/bug