UnixPB: Fix insecure downloads discovered from TrailOfBits Audit

[steelhead31]

Fix issues identified in ToB #4

Fixes #3324

Checklist

• commit message has one of the standard prefixes
• playbook changes run through VPC or QPC (if you have access)

[steelhead31]

VPC Completed OK: https://ci.adoptium.net/job/VagrantPlaybookCheck/1827/   - except for Ubuntu, fixed and completed below.

Ubuntu VPC: OK
https://ci.adoptium.net/job/VagrantPlaybookCheck/1828/

All changes have been tested locally and have worked ok.

[sxa]

Looks probably ok, although the SLES ones won't have been tested and we should verify that they will work on a SLES image first since the certs on the older SLES may have problems. Hadn't realised we had a download of an IBM Java on SLES11... Presumably because that version needed an older glibc ...

[steelhead31]

I'll run some tests on a SLES docker image, I did manage a test on a SLES 12.3 x64 vagrant box, with a custom written playbook, that simply downloads the file with those options, but I'll try running the playbook on some additional docker SLES12 & SLES15 s390x containers or similar.

[steelhead31]

Tests on SLES12 & SLES15 docker containers ok for the changed element of the Java download, for SLES12, there are many other issues related to the lack of official repositories, but these are known issues, with SLES12 being end of life.