Use private OS distribution ZIPs in preference to public ones [DI-95]

[JackPGreen]

SNAPSHOT OS distribution ZIPs (e.g. those indexed here) will no longer be generated, which causes problems with the hazelcast-docker PR builder (amongst others).

Instead, the distribution ZIPs will be uploaded to a private AWS S3 bucket, which requires authentication.

This was a non-trivial change:

• Updated the default distribution in the Docker images to be the latest released version
  • This is guaranteed to be available (without any credentials)
  • Allows the Dockerfile to be executed normally outside of a build (e.g. for the security scan)
  • "latest released" is looked up via Maven to ensure this doesn't need any explicit maintenance in future
• Added unit tests to all modified shell scripts
• Moved get_hz_dist_zip into os_build.functions (and same for EE)
• Created additional maven.functions script to support resolution of "latest released" for a given artifact
  • This has to be duplicated for OS & EE because of Docker limitations
• Added xmllint to all the runner images that build anything as required for the Maven stuff
• Updated the get_dist OS script to generate a pre-signed S3 URL to get it from S3 rather than a Maven repository
  • Because this requires authentication, had to move this from inside the image to outside to access the repository secrets
• Simplified the Dockerfile arguments - the URL resolution is now being done outside of the Dockerfile more of the time, meaning not always required
  • removed the redundant HZ_VARIANT parameter
  • removed HZ_VERSION from OS and reduced usage in EE

For testing, I've been doing what I can locally to assert the results between master and my branch are the same:

• E.G. the build-pr.yml doesn't pass locally for me on EE, I presume due to some act incompatibility - so a milestone for my PR is to get the same failure in the same place
• I've build the images locally (outside of act, just a plain docker buildx build hazelcast-os) and they build ok.
• Because of the reliance on repository secrets, it's not possible to run many tests properly

Fixes: DI-95

[JackPGreen]

@ldziedziul following a conversation with @nishaatr I've reverted removing the HZ_VERSION property, but made it explicit what it it is / isn't used for.

40ee80780818094500949572aa5914b25812968d

[nishaatr]

@ldziedziul following a conversation with @nishaatr I've reverted removing the HZ_VERSION property, but made it explicit what it it is / isn't used for.

Thanks @JackPGreen. Looks good.

@ldziedziul we are keeping the new way to decide which Docker image edition(s) to build i.e. OSS, EE or ALL. This is more explicit and neater as opposed to relying on EE/OSS Dockerfile updates. The HZ_VERSION will continue to be updated by the release pipeline as it is now to keep track of the version used for creating release and maintenance branches. I looked at the code and removing HZ_VERSION is a pain and cannot do without it - as we need to keep track of the version in the Dockerfile to create the correctly named branches

[JackPGreen]

We need to make sure that it will work with hazelcast-mono:

Workflows:

• development-release-deploy-image.yml

Modules

• hazelcast-docker-slim/pom.xml
• hazelcast-enterprise-it/pom.xml

Could you check these places?

I've looked and I don't see any issues there with this change.