Automatically perform a backup of Che server side components before attempting an upgrade

[mmorhun]

What does this PR do?

Makes Che Operator to create a backup of Che installation before upgrading it to newer version.

As operator cannot know when it will be replaced with a newer version, it is the newer operator that does the backup before updating Che to newer version. The backup is sent to internal backup server to have the behavior more predictable (and to not to guess in case several backup servers configured). Backup CRs are named after version to upgrade to: backup-before-update-to-<version> (for example: backup-before-update-to-7-36-2). Also, to be able to know the version of the operator needed to reastore the backup, cheVersion field is added to the backup CRD status.

Screenshot/screencast of this PR

N/A

What issues does this PR fix or reference?

Is a part of https://issues.redhat.com/browse/CRW-1497

How to test this PR?

1. Create a new fake version in stable channel that uses operator image from this PR. To do this modify ./bundle/stable/eclipse-che-preview-openshift/manifests/che-operator.clusterserviceversion.yaml.
2. Build catalog source image. It cannot be deployed via operator-sdk as it considers CSV not valid after our release scripts changes.
3. Run ./olm/testUpdate.sh script till waitCheServerDeploy line (it should deploy the catalog source built in previous step)
4. Approve install plan to update to the fake version.
5. Check that internal backup server is created and configured and backup CR is created.

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
• OLM bundles are 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.

Release Notes Text

Server component backup of the Che server has been introduced a few releases ago. Now it’s performed automatically before every Che upgrade.

[AndrienkoAleksandr]

It would be nice to have some unit tests for this new feature.

[codecov]

Codecov Report

Merging #1055 (c6b47ef) into main (8b1dd15) will decrease coverage by 0.32%.
The diff coverage is 19.44%.

@@            Coverage Diff             @@
##             main    #1055      +/-   ##
==========================================
- Coverage   52.52%   52.19%   -0.33%     
==========================================
  Files          62       63       +1     
  Lines        7688     7757      +69     
==========================================
+ Hits         4038     4049      +11     
- Misses       3215     3271      +56     
- Partials      435      437       +2     

Impacted Files	Coverage Δ
controllers/che/checluster_controller.go	20.00% <0.00%> (-0.44%)	⬇️
controllers/che/backup.go	21.31% <21.31%> (ø)
pkg/deploy/server/server.go	63.87% <100.00%> (-0.38%)	⬇️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 8b1dd15...c6b47ef. Read the comment docs.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: AndrienkoAleksandr, mmorhun, tolusha

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