CodeFlare Notebook has FIPS Failure messages

[jbusche]

Describe the Bug

Running the ./check-payload scan operator --spec quay.io/project-codeflare/notebook:v0.10.1 from https://github.com/openshift/check-payload.git results in FIPS failures:

--- Failure Report
+---------------------+--------------------------+-----------------------------------------------------------------------------------+--------------------------------------------+
| OPERATOR NAME       | EXECUTABLE NAME          | STATUS                                                                            | IMAGE                                      |
+---------------------+--------------------------+-----------------------------------------------------------------------------------+--------------------------------------------+
| python-39-container | /opt/app-root/bin/oc     | could not find dependent openssl version within container image: libcrypto.so.1.1 | quay.io/project-codeflare/notebook:v0.10.1 |
| python-39-container | /opt/app-root/bin/py-spy | executable is not dynamically linked                                              | quay.io/project-codeflare/notebook:v0.10.1 |
+---------------------+--------------------------+-----------------------------------------------------------------------------------+--------------------------------------------+
F1102 15:07:08.448138   81575 main.go:259] Error: run failed

Similar issues have been opened up for the CodeFlare operator https://github.com/red-hat-data-services/codeflare-operator/issues/4 and KubeRay https://github.com/red-hat-data-services/codeflare-operator/issues/5

Codeflare Stack Component Versions

Please specify the component versions in which you have encountered this bug.

Codeflare SDK: notebook:v0.10.1 MCAD: n/a Instascale:n/a Codeflare Operator: codeflare-operator:v1.0.0

Other:

Steps to Reproduce the Bug

with [check-payload](https://github.com/openshift/check-payload.git) built, 
./check-payload scan operator --spec quay.io/project-codeflare/notebook:v0.10.1

Expected Behavior

No failure messages on the check-payload scan