Generalise versioning scheme past semver (e.g. calver, unitary, or alphabetical release)

**Is your feature request related to a problem? Please describe.**

This issue is related to where #1957 was heading toward at the end of the thread, so tagging @laughedelic @JReinhold here.
Some software packages and non-software projects use different schemes than semver, for instance unitary/alphabetical release, calver, or mixed semver-calver

For instance, we're starting a documentation project that would benefit from receiving a mixed semver-calver versioning, e.g. YYYY.patch

While this is an easy non-semver version to feed to auto (cause it's still bendable into XX.YY.ZZ), having a proper YYYY.patch verison is not possible at the moment.
Is there interest in generalising the versioning scheme and add calver-related enhancement?
I'm also thinking about other projects, for instance what you peeps are doing @oesteban @yarikoptic @handwerkerd

**Describe the solution you'd like**
- generalised versioning scheme to decide formats (e.g. XX.YY instead of XX.YY.ZZ) and fields (e.g. {year}.{patch})
- automation scripts on release label(s) that collects the date and either create a pure calver release or appends semver components.

**Describe alternatives you've considered**
https://github.com/marketplace/actions/calver-release

Very brief consideration: all of our repos are based on auto, and there are just way too many features (e.g. automatic changelog) that we don't want to loose!

**Additional context**