Release v1.0.0 stable version of common (or subset of packages)

Hi 👋🏽

It's time to take common to a higher stability level. We damage the ecosystem by making breaking changes (I authored some 🙃 ) e.g. https://github.com/thanos-io/thanos/pull/8162 (pulling some dep suddenly break another dep etc.).

• Why not doing this?
• Should we have a separate common/exp module with 0.x like we do in client_golang now for experimental packages (that we can move to stable mod one day?)
• Should we be more strict on merging new code (in terms of API flexibility, naming) given it will be hard to change?
• Do we need to do any major changes before 1.0?

If we need more data on how much problematic 0.x common version is, to motivate this, I can try to research exact numbers, let me know!

cc @aknuds1 @SuperQ

Start by reviewing the current common module and the breaking-change example in PR 8162. Evaluate whether a stable v1.0.0, a separate experimental module, or broader API changes are needed. Done means the project has a decided stability policy and a concrete release plan.