standardised versioning schemes? #28

The version numbers for uv projects still follows PEP440, so it's still "v1.2.3.dev1" for those, while yarn projects already get semantic versions "1.2.3-dev.1". Maybe we want to standardise both of them to semver?

The inconsistency is a problem for the deployment of the ndc-api for example, which expects semver version strings to distinguish packages. Should we solve that problem there or standardise and always use semver for tags and releases?

See also discussion in #27