Fix regex issue in release process

[ZohebShaikh]

A release was made which had the wrong versioning,The regex should be fixed to address this.

Investigation into the issue has let me to belive that it has originated from

https://github.com/DiamondLightSource/blueapi/tree/gh-pages/fix-persistent-volume-retention-1
or

https://github.com/DiamondLightSource/blueapi/tree/gh-pages/fix-persistent-volume-retention-2

The semver in question is this

[tpoliaw]

I think the regex that's causing the problem is this one.

This is the CI run that published the bad version.

The container build failed because the version tag didn't match but there is no check in the pypi pipeline to ensure the tag is valid. setuptools_scm uses its own regex and allows kebab-case prefixes before versions in its tags.

Potential fixes:

• Add a custom tag regex to pyproject.toml to require a valid version. I'm not sure what happens if the most recent tag is not valid though. Does it jump back to the previous tag or fail?
• Rearrange the CI pipeline to make all the steps that release things out of the CI job to be dependent on a go/no-go check that requires valid version and everything building. Note that the PyPI version was published even though the container build failed.

[tpoliaw]

The pipeline's pypi / upload summary also recommends changing how we run the pypi upload so it might be worth changing that at the same time.

[ZohebShaikh]

These are all good changes to have, I think we can push all of this upstream to copier template as well.