Fix the FIPS hardware encryption issue that doesn't allow Keycloak to start

[carlosthe19916]

Bug diagnosis

• Keycloak does not support FIPS mode enabled
• Every single Keycloak instance higher than >=15.1.0 will fail to run if the OS where it is running has FIPS enabled => hence JDK.
• We can not add users using add-user-keycloak.sh hence we can not init the admin user neither the mta user

A detailed explanation is being given at keycloak/keycloak#9916

Useful links:

• https://access.redhat.com/solutions/5696401
• Keycloak does not work on systems with FIPS mode enabled keycloak/keycloak#9916
• PolicyEnforcerTest fails to start on RHEL with enabled FIPS mode quarkusio/quarkus-quickstarts#998

About this PR

Adding the JAVA_OPTS ENV variable

Note: We are not using JAVA_OPTS_APPEND (as described in the Keycloak issue comments) but JAVA_OPTS otherwise the users admin neither mta will be created.

Steps to test this PR:

Create a container image for the operator

• Check out this PR
• Create a container image for the operator using:

./mvnw clean package \
-Dquarkus.container-image.build=true \
-Dquarkus.container-image.registry=quay.io \
-Dquarkus.container-image.tag=fips \
-DskipTests

• The previous command should've created a container image called quay.io/windupeng/windup-operator-native:fips
• Tag the previous container image to use your own username:

docker tag quay.io/windupeng/windup-operator-native:fips \
quay.io/YOUR_USERNAME/windup-operator-native:fips

• Push the container image to your quay.io account.

Deploy the operator (you need an OCP instance where you have cluster-admin permissions)

• Open the file src/main/resources/k8s/def/windup.deployment.yaml and replace the line 20 to point to your custom image. So
  - image: quay.io/windupeng/windup-operator-native:latest should become - image: quay.io/YOUR_USERNAME/windup-operator-native:native:fips

• Create a namespace named mta (the name must be mta):

oc new-project mta

• Execute:

cd ./src/main/resources/k8s/def/
./script.create.all.sh

• Create a Windup instance:

oc create -f src/main/resources/k8s/examples/windup.yaml -n mta

• There should be a deployment called mta-example and the ENV variables of that deployment should contain the new ENV JAVA_OPTS with value -Dcom.redhat.fips=false

That's all. We need to keep in mind that this PR only adds a new ENV variable to the deployment, it is not changing any core behaviour of the operator

[mrizzi]

Keycloak deployment has been removed so the PR is not needed anymore.
Thanks @carlosthe19916 for having investigated this issue 👍