feat(#1656) : Jib publish strategy base on JibCli

[gansheer]

Ref #1656

Motivation

This Jib publish strategy uses the Jib Cli tool that propose the same features that the Jib maven plugin as a CLI wrapper without the need for a pom.xml as build description.

The existing builder code already creates a folder /tmp/kit-xxxxxxxxxxxxxxxxxxxxxxxxxxxx/context containing the needed dependencies, so the pom.xml used by the maven build command is not really needed to create the target Kit image.
The other main advantage is the creation of the runtime builder image does not provides any maven context/config/pom.xml, therefore the usage of a CLI allows to create this runtime builder image.

Description

• Add the Jib CLI tool into the Dockerfile of the camel-k image
• Define the Jib BuildConfig for : runtime builder image, jvm kit image, native kit image
• Add the Jib publish strategy
• Add the Jib runtime builder image creation
• Add the Jib Kit image creation
• Add registry auth managment

Release Note

feat(#1656) : Jib publish strategy base on JibCli

[squakez]

In general I think it's good to have the JIB strategy, but the operator should not depend by it. I mean that we should not have the CLI included in the container image. If a user wants to use any external tool, then it makes sense to use the pod strategy, as it already happens for Buildah and Kaniko. Even for Spectrum, I think we made a design mistake allowing it to be used within the same kamel builder command, which is creating a circular reference that has to be solved sooner or later.

[gansheer]

Closing in favor of trying out some features to use pipelines instead.