feat: Add binary compatiblity validation and start using semver

[0ffz]

• Document versioning rules (we only want breaking changes every Minecraft update)
• Add github action that validates binary compatiblity, preferably as automated as possible (kotlinx.binary-compatibility-validator seems quite nice but would require us to review added api each time and inevitably something will slip through.) The action should succeed if MAJOR was bumped on an incompatibility and compare with latest release. Dev builds ignore this.
• Consider whether we should check breaking changes with dependencies. We might want to bump these once in a while during an MC version but it might be harder to see if things break since they're not part of this project?
• Add +<minecraft-version> to version name, I think this is the best semver compliant way to show what mc version we build against