Improve documentation of version meaning in anemoi catalogue #104
Description
Currently our naming convention for versioning datasets is inconsistent and not particularly well-documented, so it's not always easy to find newer versions.
It is currently roughly:
✅ increment a version number when we add variables to a dataset
❔ maybe increment a version number when we add dates (it's inconsistent) - should adding 6 months on the end be an increment? Probably yes if we want to make people aware of more up to date versions so we can delete older ones. But datasets that have drastically different ranges of dates probably aren't.
❌ don't increment versions (i.e. definitely a new dataset) if we change resolution/source/frequency
❌ we don't increment versions if we change metadata version (which might make more sense to be a minor version?)
To-do
- Add documentation for when to increment versions
- Add some guidance that not every "version" needs to be uploaded to the catalogue (for example if it is used locally). For example first ARA dataset will be v12.