cvo: Add optional tls scanner presubmit job

A failing test of the tls-scanner-run step [1] does not
fail the whole job [2]. At least, as of the moment.
Thus, make the job optional. An always passing job has no significant value.

Thus, the job is intended to be used to verify TLS changes explicitly.
We'll depend on existing periodic testing and fix things
when a regression is reported, if not caught during merging.

Use an AWS cluster profile in combination with stronger compute nodes
to handle the tls-scanner-run step. The default node type fails to
schedule the needed pods by the step. The node type was chosen
based on other tls-scanner jobs in the openshift/release repository.

[1]: https://steps.ci.openshift.org/reference/tls-scanner-run
[2]: https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/openshift_release/76044/rehearse-76044-pull-ci-openshift-cluster-version-operator-main-tls-scanner/2031796334276644864

Author: DavidHurta

ci-operator/config/openshift/cluster-version-operator/openshift-cluster-version-operator-main.yaml

@@ -196,6 +196,17 @@ tests:
   container:
     from: src
   skip_if_only_changed: ^docs/|\.md$|^(?:.*/)?(?:\.gitignore|OWNERS|PROJECT|LICENSE)$
+- always_run: false
+  as: tls-scanner
+  optional: true
+  steps:
+    cluster_profile: aws-5
+    env:
+      COMPUTE_NODE_TYPE: m5.2xlarge
+      SCAN_NAMESPACE: openshift-cluster-version
+    test:
+    - ref: tls-scanner-run
+    workflow: ipi-aws
 zz_generated_metadata:
   branch: main
   org: openshift