Merge DevWorkspace Che operator in Che operator

[l0rd]

Is your enhancement related to a problem? Please describe.

In the DevWorkspace configuration Che operator will install both DevWorkspace operator (issue) and DevWorkspace Che operator (issue). Those are currently 2 independent operators: they can be installed even without Che. But although it makes sense for DevWorkspaec operator, DevWorkspace Che is highly coupled to Che, it does only make sense when Che is deployed.

Describe the solution you'd like

DevWorkspace Che controller and CRDs should be included in Che operator.

Sub tasks

• DWO, DWCO and CO should use CRD of the same versions DWO, DWCO and CO should use CRD of the same versions #19472
• Run DWCO and CO in a single container but in different pods Run DWCO and CO in single pod but different containers #19402
• Update operator-sdk to the latest version Update operator-sdk to the latest version #19466
• Merge DWCO and CO in a single codebase Merge DWCO and CO in a single codebase #19408

[tolusha]

@metlos suggested to merge DevWorkspace Che operator codebase into a Che Operator
@l0rd WDYT?

[l0rd]

@tolusha I am +1 for that

[nickboldt]

I'm +1 too, especially if it can be prioritied for 7.28.0 (or 7.28.x backport).

[tolusha]

@l0rd
We decided to split the task into 2 steps.
On first step [1] we run DWCO in a separate pod.
On the second [2] we merge codebase and run DWCO in the same pod.

[1] Run DWCO and CO in a single container but in different pods #19402
[2] Merge DWCO and CO in a single codebase #19408

/cc @sparkoo @metlos @skabashnyuk

[l0rd]

@tolusha it makes sense

[tolusha]

This issue is started to be an umbrella for sub-tasks.
I've removed it from the current sprint and added another one [1] which is possible to complete.

[1] #19402