chore: temporarily increase severity threshold for red hat images

Author: ivanstanev

.circleci/config.yml

@@ -708,7 +708,7 @@ jobs:
                 additional-arguments: --project-name=ubi8
                 docker-image-name: ${IMAGE_NAME_APPROVED_UBI8}
                 monitor-on-build: true
-                severity-threshold: high
+                severity-threshold: critical
                 target-file: Dockerfile.ubi8
             - run:
                 command: |
@@ -741,7 +741,7 @@ jobs:
             - snyk/scan:
                 docker-image-name: snyk/kubernetes-operator:${OPERATOR_TAG}
                 monitor-on-build: true
-                severity-threshold: high
+                severity-threshold: critical
                 target-file: snyk-operator/build/Dockerfile
             - run:
                 command: ./scripts/slack/notify_failure.py "${CIRCLE_BRANCH}" "${CIRCLE_JOB}" "${CIRCLE_BUILD_URL}" "${CIRCLE_PULL_REQUEST}" "${SLACK_WEBHOOK}"

.circleci/config/jobs/@jobs.yml

@@ -285,7 +285,7 @@ publish:
         additional-arguments: --project-name=alpine
     - snyk/scan:
         docker-image-name: ${IMAGE_NAME_APPROVED_UBI8}
-        severity-threshold: high
+        severity-threshold: critical
         target-file: Dockerfile.ubi8
         monitor-on-build: true
         additional-arguments: --project-name=ubi8
@@ -319,7 +319,7 @@ publish:
           echo "export OPERATOR_TAG=${OPERATOR_TAG}" >> $BASH_ENV
     - snyk/scan:
         docker-image-name: snyk/kubernetes-operator:${OPERATOR_TAG}
-        severity-threshold: high
+        severity-threshold: critical
         target-file: snyk-operator/build/Dockerfile
         monitor-on-build: true
     - run: