The new value in JBOSS_HOME in EAP 8 S2I images impacts the EAP Operator

This issue is about the new operator images:

• OPERATOR IMAGE="registry-proxy.engineering.redhat.com/rh-osbs/jboss-eap-7-eap73-rhel8-operator:2.4-9"
• OPERATOR BUNDLE IMAGE="registry-proxy.engineering.redhat.com/rh-osbs/jboss-eap-7-eap73-rhel8-operator-bundle:2.4-8"

which will support the new EAP8 images:

• registry-proxy.engineering.redhat.com/rh-osbs/jboss-eap-8-tech-preview-eap8-openjdk17-builder-openshift-rhel8:1.0.0.Beta-7
• registry-proxy.engineering.redhat.com/rh-osbs/jboss-eap-8-tech-preview-eap8-openjdk17-runtime-openshift-rhel8:1.0.0.Beta-5
• registry-proxy.engineering.redhat.com/rh-osbs/jboss-eap-8-tech-preview-eap8-openjdk11-builder-openshift-rhel8:1.0.0.Beta-7
• registry-proxy.engineering.redhat.com/rh-osbs/jboss-eap-8-tech-preview-eap8-openjdk11-runtime-openshift-rhel8:1.0.0.Beta-5

When you create a WildFlyServer CR which contains:

  storage:
    volumeClaimTemplate:
      apiVersion: v1
      kind: PersistentVolumeClaim
      spec:
        resources:
          requests:
            storage: 100M

then, in the EAP POD generated by the EAP operator there is:

      volumeMounts:
        - name: tx-server-volume
          mountPath: /opt/eap/standalone/data

since JBOSS_HOME is now "/opt/server", the "mountPath" value
should be "/opt/server/standalone/data", not "/opt/eap/standalone/data"