Graduate our CRDs and watch for backwards-incompatible changes #2556
Description
In order to make it easier for consumers of toolhive to use it and its operator, we should stop changing our APIs and introduce a bit more rigor.
On a high level we should:
- add a CI job to warn us if a change to a CRD is backwards incompatible
- unify the API groups of the CRDs, e.g. get rid of stacklok.dev in the API groups
- bump their version to e.g. v1beta1
- add the needed infrastructure to potentially add a v1beta2 if an incompatible change is needed