Add tls-scanner-run to RHOAI e2e job

Adds tls-scanner-run as a test step to the opendatahub-operator-rhoai-e2e
job to enforce TLS compliance scanning on deployed RHOAI components.

Configuration:
- tls-scanner-tool base image from OCP 4.22
- Runs as final test step (blocks PR on failure, can be overridden)
- PQC_CHECK: true (enable post-quantum crypto checks)
- SCAN_NAMESPACE: redhat-ods-operator,redhat-ods-applications

Follows the pattern from compliance-operator (PR #78651).

Reference: https://steps.ci.openshift.org/reference/tls-scanner-run
Related: RHOAIENG-61076

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

Author: ugiordan

ci-operator/config/opendatahub-io/opendatahub-operator/opendatahub-io-opendatahub-operator-main.yaml

@@ -7,6 +7,10 @@ base_images:
     name: "4.19"
     namespace: origin
     tag: operator-sdk
+  tls-scanner-tool:
+    name: "4.22"
+    namespace: ocp
+    tag: tls-scanner-tool
   ubi:
     name: ubi-minimal
     namespace: ocp
@@ -121,6 +125,8 @@ tests:
       SOURCE_IMAGE_REF: opendatahub-operator-rhoai
     env:
       IMAGE_REPO: opendatahub-operator
+      PQC_CHECK: "true"
+      SCAN_NAMESPACE: redhat-ods-operator,redhat-ods-applications
     pre:
     - ref: ipi-install-rbac
     - ref: opendatahub-operator-e2e-cluster-preflight-health-check
@@ -152,6 +158,7 @@ tests:
           cpu: 2000m
           memory: 3Gi
       timeout: 3h0m0s
+    - ref: tls-scanner-run
     workflow: generic-claim
 - as: opendatahub-operator-image-mirror
   postsubmit: true