feat: update jolokia to 2.6.0

[ash-thakur-rh]

Summary

• Bump Jolokia from 2.1.2 to 2.6.0 for jkube-java (Java 21) and jkube-java-17 images
• Add new Jolokia 2.6.0 modules for both module paths (org.eclipse.jkube.jolokia and jboss.container.jolokia)
• Add Jolokia sanity tests to all three test scripts
• jkube-java-11 stays on Jolokia 2.1.2 (Jolokia 2.4.0+ requires Java 17 minimum)

Details

Jolokia 2.6.0 requires Java 17+, so only the Java 17 and Java 21 images are upgraded:

• jkube-java.yaml -> org.eclipse.jkube.jolokia 2.1.2 → 2.6.0
• jkube-java-17.yaml -> jboss.container.jolokia jkube-2.1.2 → jkube-2.6.0
• jkube-java-11.yaml -> unchanged (remains on 2.1.2)

Modules added:

• modules/org.eclipse.jkube.jolokia/2.6.0/
• modules/jboss.container.jolokia/jkube-2.6.0/

Tests added (all 3 test scripts):

• Verify jolokia-opts script is executable
• Verify jolokia-opts produces correct -javaagent output
• Verify AB_JOLOKIA_OFF=true disables Jolokia agent
• Verify JBOSS_CONTAINER_JOLOKIA_MODULE env var is set
• Update JOLOKIA_VERSION env check to 2.6.0 for java and java-17

Test plan

• Build all three images (jkube-java, jkube-java-17, jkube-java-11)
• Run scripts/test-jkube-java.sh, scripts/test-jkube-java-17.sh, scripts/test-jkube-java-11.sh
• Verify Jolokia agent loads correctly at container runtime