jkube-images: Consider stop using your own container detection

[manusa]

Description

From internal mail to middleware-containers@redhat.com:

Since this comes up every now and again: Please stop using any shell script wrappers that look at cgroup interface files in order to "detect" the set cpu/memory limits if you already know that you are running on OpenJDK for your Java workloads in containers.

OpenJDK upstream has support for it out of the box for a while now.
See:
https://developers.redhat.com/articles/2022/04/19/java-17-whats-new-openjdks-container-awareness

So if one of your containers still have $JBOSS_CONTAINER_JAVA_JVM_MODULE/container-limits and friends, please consider removing them in your latest images. That's what we've done in the Red Hat OpenJDK containers, like ubi9/openjdk-11 et. al.

We need to remove these scripts from the applicable images (JDK 17+) in https://github.com/jkubeio/jkube-images/ repository.