[main] Aligning openssl versions across toolchain build phases.

[PawelWMS]

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

• The toolchain has been rebuilt successfully (or no changes were made to it)
• The toolchain/worker package manifests are up-to-date
• Any updated packages successfully build (or no packages were changed)
• Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
• Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
• All package sources are available
• cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/tools/cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json)
• LICENSE-MAP files are up-to-date (./SPECS/LICENSES-AND-NOTICES/data/licenses.json, ./SPECS/LICENSES-AND-NOTICES/LICENSES-MAP.md, ./SPECS/LICENSES-AND-NOTICES/LICENSE-EXCEPTIONS.PHOTON)
• All source files have up-to-date hashes in the *.signatures.json files
• sudo make go-tidy-all and sudo make go-test-coverage pass
• Documentation has been updated to match any changes to the build system
• Ready to merge

---

Summary

While working on #2515, @mfrw noticed that we're building the 1.1.1g version of openssl in the 1^st phase of the toolchain builds, while in general Mariner is on the 1.1.1k version. This PR makes the built versions consistent.

Change Log

• Made sure we build the 1.1.1k version of openssl consistently across toolchain build phases.

Does this affect the toolchain?

Yes.

Associated issues

• [main] upgrading libarchive to v3.6.0 #2515

Test Methodology

• Pipeline toolchain build: 175989

[ghost]

LGTM, just one request!

[mfrw]

LGTM :)