Improve error message when `from` image cannot be found

Description of the issue: When jib cannot find image specified in from build fails with this not very explanatory message. I also think that it is a little bit missleading because Getting base image ghostbuster91/test-jib2.. looks fine.

❯ ./gradlew jib
warning: Base image 'ghostbuster91/test-jib2' does not use a specific image digest - build may not be reproducible

Containerizing application to ghostbuster91/test-jib...

Retrieving registry credentials for registry.hub.docker.com...
Getting base image ghostbuster91/test-jib2... <-- HERE IT LOOKS OK
Building dependencies layer...
Building classes layer...
Building resources layer...
Retrieving registry credentials for registry.hub.docker.com...

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':jib'.
> Build image failed

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 11s
2 actionable tasks: 1 executed, 1 up-to-date

Expected behavior: IMO the best way would be to fail when executing Getting base image ghostbuster91/test-jib2.. At least some better error message should be provided.

Steps to reproduce: Just make a type when declaring from image. Environment: Ubuntu 18.04

jib-gradle-plugin Configuration:

plugins {
    id 'com.google.cloud.tools.jib' version '0.9.6'
}
apply plugin: 'java'

group 'test-jib'
version '1.0-SNAPSHOT'

sourceCompatibility = 1.8

repositories {
    mavenCentral()
}

dependencies {
    testCompile group: 'junit', name: 'junit', version: '4.12'
}

jib {
    from {
        image = 'ghostbuster91/test-jib2'
    }
    to {
        image = 'ghostbuster91/test-jib'
    }
    container {
        mainClass = 'Main'
    }
}

Log output:

Additional Information:

[briandealwis]

Great! We can provide a better message for RegistryErrorExceptions:

Caused by: com.google.cloud.tools.jib.registry.RegistryErrorException: Tried to pull image manifest for registry.hub.docker.com/ghostbuster91/test-jib-2:latest but failed because: manifest unknown | If this is a bug, please file an issue at https://github.com/GoogleContainerTools/jib/issues/new

[briandealwis]

I meant to close this: #697 surfaces the RegistryErrorException which addresses the opaque Execution failed for task ':jib'. message in this issue. The problem with the misleading registry auth is #758.