test Quarkus image build and deployment as well

[Ladicek]

Currently, we only let the quarkus-openshift extension generate the YAML resources. We then delegate to oc start-build --from-dir=target --follow for building the image and oc apply -f target/kubernetes/openshift.yml for deploying the application.

This is fine and needs to be tested. But we also need to test -Dquarkus.container-image.build for building the image and -Dquarkus.kubernetes.deploy for deploying the application.

[mjurc]

What we need right now:

1. Test (and if it works, programmatic support) for S2I build - something along the lines of oc new-app openjdk-11-rhel7 https://github.com/quarkusio/quarkus-quickstarts.git --context-dir=getting-started --name=getting-started. Basically letting OpenShift build the app through Maven from a repo.
2. Test (and if it works, programmatic support) for quarkus-openshift extension. That's described in the issue description.
3. quarkus-workshops. I'm currently deconstructing this, since it's a bit of a hard nut to crack. What the workshop tells user to do is to build the native image app, build a docker image with docker build with that app's native image, then push the image somewhere and use it in pre-defined OpenShift descriptor.