Description:
Newer versions of the OpenJDK-runtime images do not contain the `tar` and `rsync` tools required to perform the `oc cp` and `oc rsync` commands available in the oc cli tool.

This was broken recently and the tool is present in older versions of the openjdk -runtime images. I have provided examples below.

Examples:
Working image: registry.access.redhat.com/ubi8/openjdk-17-runtime@sha256:43618c504657b12e121945ad6c52ce426758fbd2158b820a9fc5babd2970bdde
Broken image: registry.access.redhat.com/ubi8/openjdk-17-runtime@sha256:934440e9a450e960dee403e7365169ca88cab52e95a28801ddc1e9d80a8cd601

Analysis:

The codebase for this appears to be here:
https://github.com/jboss-container-images/openjdk

These look like the two commits might be the culprit:
https://github.com/jboss-container-images/openjdk/commit/273ad2f9be515c6b3ce019c90522ca369d32290c

https://github.com/jboss-container-images/openjdk/commit/7be7e7142e5f161f2e9775a23a298432b59f3549

I built the images with `cekit` and can confirm those two commits appear to be causing this issue.

Output from built images: (commit SHAs)
Tar not present: 2254ad951640aa0def09de6a070da93364e7ea41
Tar present: dcbc13f9f52ad75ee0390c1296d130d12185b345

Request:
A customer has requested that the `tar` and `rsync` tools be returned to the images as this breaks the `oc cp` and `oc rsync` functionality that they use regularly. If this is not possible, please provide justification/reasoning why this change was performed to the image.
Currently they are working around the issue by building a custom image with the runtime as the base.