fix: allow pushing images with different arch/os to docker daemon

[mpeddada1]

Fixes #4265

• Avoid throwing exception when building image with mismatched arch/os to the local docker daemon.
• Follow convention of using event handlers to log warning when building for matching os/arch. Example:

  jib/jib-core/src/main/java/com/google/cloud/tools/jib/builder/steps/PullBaseImageStep.java

  Line 225 in b06b001

  eventHandlers.dispatch(LogEvent.debug("mirror config: " + registry + " --> " + mirror));

[mpeddada1]

Notes on kokoro-ubuntu timeout:

• The job passed on f2d886b but started failing after test for arm64 was added.

Unable to reproduce locally with ./gradlew clean build :jib-core:integrationTest.

kokoro-macos:

• The job is failing during job start up:

++ docker-machine ls
NAME   ACTIVE   DRIVER   STATE   URL   SWARM   DOCKER   ERRORS
++ docker-machine start default
Docker machine "default" does not exist. Use "docker-machine ls" to list machines. Use "docker-machine create" to add a new one.

[mpeddada1]

[Update on CI] Splitting the test methods up into separate test classes no longer causes the builds to be stuck. Ready for another round of review.

[geoand]

Thanks for the fix folks!

As we are seeing someone reporting something similar in Quarkus, would it be possible to know an approximate timeline for a release of jib-core that will contain the fix?
Thanks!

[calebAtIspot]

should https://github.com/GoogleContainerTools/jib/blob/master/docs/faq.md#how-do-i-specify-a-platform-in-the-manifest-list-or-oci-index-of-a-base-image be updated? It still says "Does not support pushing to a Docker daemon"