CRD and controller for OS versions

[mudler]

In order to be able to select available versions to upgrade our nodes into from UI or either kubectl, we need a generic ManagedOSVersion CRD/controller and a ManagedOSVersionChannel CRD to represent the version we want to upgrade into, and how we get all the lists of available versions. This will also help us later on with moving image validation steps inside the kubernetes cluster with a kubewarden policy (as we can validate releases both while fetching new ones, and while applying them)

• Split ros-operator into its own repo #67
• ManagedOS upgrade command is hardcoded #59
• Drop integration tests, add e2e tests with kind rancher-sandbox/rancheros-operator#7
• CRD: ManagedOSVersion #78
• Consume ManagedOSVersion from ManagedOS #64
• CRD: ManagedOSVersionChannel #63
• Custom syncer for ManagedOSVersionChannel #84
• Respect version in minVersion field in ManagedOSImageVersion #85
• e2e upgrade tests #86
• Create a default ManagedOSVersionChannel for os2 #87
• Handle error events rancher-sandbox/rancheros-operator#16
• Cleanup of ManagedOSVersion orphans rancher-sandbox/rancheros-operator#17
• Sync service ticker is hardcoded rancher-sandbox/rancheros-operator#18
• Kubewarden policy to validate cosign images elemental-toolkit#1183

Notes

API defintions: https://github.com/rancher-sandbox/os2/blob/master/pkg/apis/rancheros.cattle.io/v1/os.go#L28

[mudler]

Closing this as we have the mechanism in place. we have already follow-ups for the low-hanging fruit work