fix(hive): Fix TLS problems by switching back to Java 11

[sbernauer]

Description

Should fix broken tests introduced in #581

To sum this up for the suits:

• We used to ship the pre-built Hive binary in a container with java 11 runtime and everything worked (this was presumably built on java 8 )
• After building ourselves from source (with java 8 ) we switched the java runtime in the container from 11 to 8 and some weird tls stuff broker
• Switching back to 11 in the container fixes it

The log of the failing TLS access to MinIO is attached

hive-metastore-default-0.log

See https://stackable-workspace.slack.com/archives/C031A5BEFS7/p1713185172557459 for details

Definition of Done Checklist

• Not all of these items are applicable to all PRs, the author should update this template to only leave the boxes in that are relevant
• Please make sure all these things are done and tick the boxes

- [x] Changes are OpenShift compatible
- [x] All added packages (via microdnf or otherwise) have a comment on why they are added
- [x] Things not downloaded from Red Hat repositories should be mirrored in the Stackable repository and downloaded from there
- [x] All packages should have (if available) signatures/hashes verified
- [ ] Does your change affect an SBOM? Make sure to update all SBOMs
- [x] Add an entry to the CHANGELOG.md file
- [ ] Integration tests ran successfully

TIP: Running integration tests with a new product image

The image can be built and uploaded to the kind cluster with the following commands:

bake --product <product> --image-version <stackable-image-version>
kind load docker-image <image-tagged-with-the-major-version> --name=<name-of-your-test-cluster>

See the output of bake to retrieve the image tag for <image-tagged-with-the-major-version>.

[Maleware]

LGTM! Thanks again!