Use semantic versioning

Please use (and update) actual version numbers in the pom.xml file for this project. The current version, canary, hasn't been updated since 2017 and makes it hard to find the source of issues like this. Naming versions elsewhere such as release documentation would be just fine, of course.

When NamelessMC v2 is released, the API will become stable and I will also look into pushing builds to maven central