Prepare for WTO 1.10 release

[AObuchow]

What does this PR do?

• Updates the changelog, refer to Update tooling for OCP 4.15; update base images web-terminal-tooling#69 for tooling version updates
• Updates CSV version to WTO 1.10
• Updates base images for controller build
• Updates minimum OpenShift version annotation to OpenShift 4.15

Is it tested? How?

Testing requires an OpenShift 4.15 cluster.

I've built the controller, index and bundle images from this PR and pushed them to quay.io/aobuchow/wto-controller:1.10, quay.io/aobuchow/wto-bundle:1.10 & quay.io/aobuchow/wto-index:1.10 respectively.

The accompanying WTO tooling image (built from this PR) has also been pushed to quay.io/aobuchow/wto-tooling:1.10.

To test the images, set the WTO_IMG, BUNDLE_IMG & INDEX_IMG environment variables to the above-mentioned repos, i.e:

export WTO_IMG=quay.io/aobuchow/wto-controller:1.10 && export BUNDLE_IMG=quay.io/aobuchow/wto-bundle:1.10 && export INDEX_IMG=quay.io/aobuchow/wto-index:1.10

Then run make install from the root of this repo.

WTO 1.10 should be installed (and viewable on the Installed Operators page of the OpenShift console) using the images built from this PR.

Note: Running the version of WTO installed will still be using quay.io/wto/web-terminal-operator:next instead of the image built from this PR, set to WTO_IMG. To actually test out the controller image, find the web-terminal-operator clusterserviceversion in the openshift-operators namespace, and modify the spec.containers.image field to use the controller image built from this PR. E.g.:

apiVersion: operators.coreos.com/v1alpha1
kind: ClusterServiceVersion
(...)
spec:
(...)
  install:
    spec:
      deployments:
        - name: web-terminal-controller
          spec:
(...)
              spec:
                containers:
                  - env:
                      - name: POD_NAME
                        valueFrom:
                          fieldRef:
                            fieldPath: metadata.name
                      - name: OPERATOR_NAME
                        value: web-terminal-operator
                      - name: RELATED_IMAGE_web_terminal_tooling
                        value: 'quay.io/wto/web-terminal-tooling:latest'
                      - name: RELATED_IMAGE_web_terminal_exec
                        value: 'quay.io/eclipse/che-machine-exec:nightly'
-                   image: 'quay.io/wto/web-terminal-operator:next'
+                   image: 'quay.io/aobuchow/wto-controller:1.10'
                    imagePullPolicy: Always
                    name: web-terminal-controller
                    resources: {}
                serviceAccountName: web-terminal-controller

The web-terminal-controller deployment should spawn a new pod with the updated container, and you should be able to create web terminals.

A future PR could automate this process of updating the CSV for testing the controller image (as this confused me a bit while working on this PR).

[che-bot]

❌ E2E Happy path tests failed ❗

See Details

- Jenkins job - [

- Use comment "[wto-ci-test]" to rerun happy path E2E test.

[che-bot]

❌ E2E Happy path tests failed ❗

See Details

- Jenkins job - [

- Use comment "[wto-ci-test]" to rerun happy path E2E test.