Cannot generate releases from the same commit as prereleases.

Since we need to vote on releases, we create "(\d+).(\d+).(\d+).dev(\d+)" release candidates until a vote passes and then create the "(\d+).(\d+).(\d+)" release based on the release candidate with the passing vote.

Having both tags present on the same commit causes issues when building the release tarballs in CI.

As evidenced in this recent pipeline: https://github.com/apache/buildstream/actions/runs/6270069538, we can observe that while building wheels, we were getting `2.1.0.dev0` wheels when a `2.1.0` tag is present.

I have filed an upstream issue as I currently suspect the problem to be either a bug in versioneer, or a misconfiguration of versioneer on our part: https://github.com/python-versioneer/python-versioneer/issues/380

Start with the linked GitHub Actions pipeline and the upstream Versioneer issue #380 to reproduce how tags on the same commit affect wheel versioning. Trace the release-tarball and wheel-building workflow; done means a stable release tag produces stable-version wheels rather than the prerelease version when both tags are present.

Written by the indexing model from the issue text.