WINDUP-3763 Added 'multi-arch' profile to multi-arch CLI container build

[mrizzi]

https://issues.redhat.com/browse/WINDUP-3763

The idea is to have the Windup CLI container (not the other containers) built for multiple architecture so that the Windup CLI can be easily consumed leveraging docker/podman.

The changes are meant to "not change anything" meaning:

• the default profile (enabled by default) keeps running the JKube kubernetes-maven-plugin so that a local CLI container image is created and pushed to local to local Docker daemon/Podman service. No changes to any command are required for running this (i.e. mvn clean install will work as before)
• the multi-arch profile, when enabled (i.e. providing -Dmulti-arch option) with disable the default profile and enable the jib-maven-plugin run a JIB container build.
  The multi-arch build has some limitations (ref. How do I specify a platform in the manifest list (or OCI index) of a base image?): the main one for us is that the images must be pushed to a remote registry because this kind of build "Does not support pushing to a Docker daemon [...] or building a local tarball"
• the values (already used) for previously configuring the JKube kubernetes-maven-plugin have been moved to be properties so that they have been used also for the jib-maven-plugin configuration hence zeroing the maintenance overhead in having 2 plugins

Using the jib-maven-plugin is the only viable option because:

• JKube kubernetes-maven-plugin doesn't support yet multi-arch builds (ref. Support for <buildx> and Support for multiple platforms in jib build strategy issues)
• Fabric8 docker-maven-plugin supports Multi-Architecture Build but, since docker and podman are not consistent in the buildx feature for running multi-arch builds, adopting this plugin would have dropped support for podman in this project and it wasn't a suitable option

Testing

1. mvn clean install -DskipTests will prove everything works as before
2. mvn clean install -DskipTests -f cli/ -Dmulti-arch -Ddocker.name.windup.cli=quay.io/<your_quay_id>/windup-cli-openshift will let you test the multi-arch build worked (keep in mind this, as described above, will push the images to the <your_quay_id> account, so podman login quay.io must be executed in other to be authorized to push).
   An example of such a build is available at https://quay.io/repository/mrizzi/windup-cli-openshift?tab=tags