Cleanup our versioning scheme #46
Description
We are currently increasing patch versions when developing towards a new version (and introducing new features). This has 2 issues:
1: We are not being semver compliant. According to semver we should be incrementing the minor version when introducing new features.
2: We are making a new stable api release with in-development features. This locks us into not being able to make changes until the next minor version is actually released, which is unfortunate.
The goal of this ticket is to come up with a better way of handling versions and adjusting tooling / communicating it to the team.
One option to consider is gating all in-development features behind an unstable feature gate: https://github.com/WebAssembly/component-model/blob/main/design/mvp/WIT.md#feature-gates. If it's decided to go this way, we should check that @unstable is properly supported by all tools we use.
Probably relevant issue: bytecodealliance/wasmtime#10198