Detect container runtime when using Jib

[geoand]

The detection uses the same method Quarkus already
used when building the native binary using a container build

Fixes: #24231

[gsmet]

LGTM. I wonder if we should backport it given the current behavior is not aligned with other parts of the code?

[geoand]

I am not sure... All the code changes are internal, but there is a slight chance some extension could depend on the Util and break....

I would say let's not backport for now but if this is requested, I can do a 2.7 specific change that just copies the detection code.

[quarkus-bot]

This workflow status is outdated as a new workflow run has been triggered.

Failing Jobs - Building a6745e0

Status	Name	Step	Failures	Logs	Raw logs
✔️	JVM Tests - JDK 11
✖	JVM Tests - JDK 17	Build	Failures	Logs	Raw logs

Failures

⚙️ JVM Tests - JDK 17 #

- Failing: integration-tests/container-image/maven-invoker-way 

📦 integration-tests/container-image/maven-invoker-way

✖ Failed to execute goal org.apache.maven.plugins:maven-invoker-plugin:3.2.2:run (integration-tests) on project quarkus-integration-test-container-image-invoker: 1 build failed. See console output above for details.

[geoand]

I'll need to check the failure, it might be related

[geoand]

The failure does not seem related actually, but I'll restart CI just to be on the safe side

[jesperpedersen]

@gsmet @geoand A backport - in some form - to 2.7 would help the Quarkus Operator SDK in its native builds, so it would be greatly appreciated
@metacosm FYI

[geoand]

Let's keep this in mind for the next 2.7 release.

[gsmet]

I made a specific backport with backwards compatibility here: #24291 .