setup ci flow for testing quarkus deployment against openshift sandbox

[maxandersen]

Description

we've have multiple releases where one or more of the kubernetes / openshift deployment mechanisms fails.

That could have been captured if we had a basic smoke test of those deploy options.

Implementation ideas

we have option of using openshift developer sandbox - lets us test both kubernetes and openshift flows.

idea is to setup a job dedicated to this testing.

in future we could add others for aws, azure, cloud etc.

notes from chat:

@iocanel: once we have that we need to optionally enable this one: https://github.com/quarkusio/quarkus/tree/main/integration-tests/kubernetes/maven-invoker-way/src/it/openshift-s2i-build-and-deploy

@geoand: during testing I did:

mvn clean  package -Dquarkus.kubernetes.deploy=true -DskipTests -Dquarkus.package.type=legacy-jar

mvn clean  package -Dquarkus.kubernetes.deploy=true -Dquarkus.openshift.build-strategy=docker -DskipTests -Dquarkus.package.type=legacy-jar -Dquarkus.openshift.jvm-dockerfile=src/main/docker/Dockerfile.legacy-jar

mvn  clean package -Dquarkus.kubernetes.deploy=true -Dquarkus.openshift.build-strategy=docker -DskipTests

mvn  clean package -Dquarkus.kubernetes.deploy=true -DskipTests

mvn clean  package -Dquarkus.kubernetes.deploy=true -DskipTests -Dquarkus.package.type=uber-jar

[quarkus-bot[bot]]

/cc @geoand