feat: Import Devworkspace Che Operator

[metlos]

What does this PR do?

This imports the Devworkspace Che Operator as a new controller inside che-operator.

The minimum amount of changes have been made to both codebases for the stuff to work.
In another words, the new controller pkg/controller/devworkspace is essentially still
completely standalone. It even still runs in its own reconcile loop even though it
reconciles CheCluster which is also reconciled by the main che controller.

The significant changes are are concentrated in cmd/manager/main.go, which sets the whole
show up.

In pkg/deploy/dev-workspace, we have a new approach for installing the devworkspace support.
The operator exits after a successfull installation, relying on Kubernetes to restart it.
When intialized again, it sees the CRDs for devworkspaces present in the cluster and
initializes the devworkspace reconciler.

Screenshot/screencast of this PR

N/A

What issues does this PR fix or reference?

eclipse-che/che#19408

How to test this PR?

1. Install che-operator
2. Remove the DWCO container for the che-operator deployment (not yet done in this PR)
3. Change the che-operator image to quay.io/lkrejci/che-operator:issue-19408
4. Enable devworkspaces in the CheCluster CR
5. Notice the che-operator restart automatically after installation of Devworkspaces
6. Try to create a devfile v2.
7. Rejoice.

PR Checklist

As the author of this Pull Request I made sure that:

• The Eclipse Contributor Agreement is valid
• Code produced is complete
• Code builds without errors
• Tests are covering the bugfix
• Custom resource definition file is up to date
• Nightly OLM bundle is up to date
• The repository devfile is up to date and works
• Sections What issues does this PR fix or reference and How to test this PR completed
• Relevant user documentation updated
• Relevant contributing documentation updated
• CI/CD changes implemented, documented and communicated

Reviewers

Reviewers, please comment how you tested the PR when approving it.

[sparkoo]

/retest

[sparkoo]

/test v7-stable-to-nightly

[sparkoo]

/test v7-stable-to-nightly

[tolusha]

https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/origin-ci-test/pr-logs/pull/eclipse-che_che-operator/925/pull-ci-eclipse-che-che-operator-main-v7-stable-to-nightly/1423981878754414592/artifacts/stable-to-nightly/stable-to-nightly/artifacts/eclipse-che/che-operator-687f7b5599-dppmc/che-operator.log

E0807 14:02:57.890476       1 reflector.go:138] sigs.k8s.io/controller-runtime/pkg/cache/internal/informers_map.go:224: Failed to watch *v1alpha1.KubernetesImagePuller: failed to list *v1alpha1.KubernetesImagePuller: kubernetesimagepullers.che.eclipse.org is forbidden: User "system:serviceaccount:eclipse-che:che-operator" cannot list resource "kubernetesimagepullers" in API group "che.eclipse.org" at the cluster scope

[skabashnyuk]

• github.com/gliderlabs/ssh v0.2.2 https://dev.eclipse.org/ipzilla/show_bug.cgi?id=23642
• github.com/emirpasic/gods v1.12.0 https://dev.eclipse.org/ipzilla/show_bug.cgi?id=23643
• github.com/go-git/go-billy v5.0.0 https://dev.eclipse.org/ipzilla/show_bug.cgi?id=23644
• github.com/jbenet/go-context d14ea06fba99483203c19d92cfcd13ebe73135f4 https://dev.eclipse.org/ipzilla/show_bug.cgi?id=23645
• github.com/kevinburke/ssh_config 01f96b0aa0cdcaa93f9495f89bbc6cb5a992ce6e https://dev.eclipse.org/ipzilla/show_bug.cgi?id=23646
• github.com/lucasjones/reggen 37ba4fa293bb40d3e1d805ba3545bfaab688d669 https://dev.eclipse.org/ipzilla/show_bug.cgi?id=23647
• github.com/redhat-cop/operator-utils v0.1.0 https://dev.eclipse.org/ipzilla/show_bug.cgi?id=23648
• github.com/devfile/api v2.0.0 https://dev.eclipse.org/ipzilla/show_bug.cgi?id=23649
• github.com/devfile/devworkspace-operator 108b1f1fbe4574f1a47a7810b7d877684785a6d9 https://dev.eclipse.org/ipzilla/show_bug.cgi?id=23650

[sparkoo]

https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/origin-ci-test/pr-logs/pull/eclipse-che_che-operator/925/pull-ci-eclipse-che-che-operator-main-v7-stable-to-nightly/1423981878754414592/artifacts/stable-to-nightly/stable-to-nightly/artifacts/eclipse-che/che-operator-687f7b5599-dppmc/che-operator.log

E0807 14:02:57.890476       1 reflector.go:138] sigs.k8s.io/controller-runtime/pkg/cache/internal/informers_map.go:224: Failed to watch *v1alpha1.KubernetesImagePuller: failed to list *v1alpha1.KubernetesImagePuller: kubernetesimagepullers.che.eclipse.org is forbidden: User "system:serviceaccount:eclipse-che:che-operator" cannot list resource "kubernetesimagepullers" in API group "che.eclipse.org" at the cluster scope

I've tested update from 7.34.0 into this PR version, and it works fine. However, I don't know details of the CI test deployment. I don't have imagepuller enabled (I guess, I don't know how to do it).
It's very hard to get anything from the CI job. I don't know where to find CheCluster, che-operator templates, che-operator image... I cannot find it in artifacts.

cc: @tolusha

[sparkoo]

/retest

[sparkoo]

/retest

[tolusha]

I will take a look ci/prow/v7-stable-to-nightly

[tolusha]

Here is a test script which is run on OpenShift CI.
So, it starts requiring cluster roles now [2]. I think a fix will be a pretty simple. But I would like to know why these changes are required now.

[1] https://github.com/eclipse-che/che-operator/blob/main/.ci/oci-nightly-update.sh
[2] https://github.com/eclipse-che/che-operator/blob/main/config/rbac/role.yaml#L121-L126

[skabashnyuk]

@tolusha @metlos @sparkoo #925 (comment) all CQs has been approved.

[sparkoo]

I won't be available until end of the week. I have no more comments to this issue except failing CI job, which I don't know how to properly fix. I have tested the PR and it is working fine for me. So I'm giving it a green.

@tolusha please feel free to merge when you're happy with the PR

[openshift-ci]

New changes are detected. LGTM label has been removed.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: metlos, sparkoo

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[tolusha]

/retest

[tolusha]

/test v8-multi-host-next-deployment