Add a skip about CRD domains

[calebschoepp]

See here for a draft of what this change looks like.

[bacongobbler]

I'm in support of this change. This does make a point that SpinKube sub-projects must all operate under the guise of SpinKube, rather than the other way around. This also ensures that sub-projects can evolve and/or be renamed without having to break apps running in userspace (Kubernetes).

[calebschoepp]

I'm looking for an approval from the main SpinKube projects before merging to make sure we have consensus. Tagging the appropriate people to try and get the approvals so we can move this forward.

Runtime Class Manager Maintainers: @flavio OR @voigt OR @0xE282B0 could you please take a look.

[bacongobbler]

One quick thought here: we don't have documentation anywhere that describes how to upgrade from one version of spin-operator to the next, correct? If so we'd probably want to call out the breaking change in those docs.

I think the docs only talk about how to bootstrap a cluster from scratch, so we don't have to worry too much about upgrade paths, but worth keeping in mind.

[devigned]

I approve of this proposal and believe that the early we can do this the better. It will be a breaking change, but it will be less impactful the sooner we do it.

[calebschoepp]

In a SpinKube community meeting we had expressed the desire to have approval from each sub-project. The main approval missing is from the runtime-class-manager.

@flavio @0xE282B0 @voigt I'll give y'all to the end of the week to comment and otherwise I'll assume that you have no strong opinions here and I'll go forward with merging this skip.