jobs of type `docker` with `deployment` should already tag the image locally

[epDHowwD]

When defining jobs of type docker with deployment it would be handy if runing the job already tags the image for deployment. It is clear that a local execution should not push the image to the target registry. However, if the image is at least tagged locally, a follow-up job would be able to use the image under the deployment name already.

Example:

    {
        "name": "build-installer-test-base",
        "type": "docker",
        "docker_file": "infrabox/test-install/Dockerfile",
        "build_context": "../..",
        "build_only": true,
        "resources": { "limits": { "cpu": 1, "memory": 2048 } },
        "deployments": [{
            "type": "docker-registry",
            "host": "v2-registry.dhcp.wdf.sap.corp",
            "repository": "infrabox/datahub-operator/com.sap.datahub.linuxx86_64/installer-test-base"
        }]
    },{
        "name": "test-install",
        "type": "docker-image",
        "image": "v2-registry.dhcp.wdf.sap.corp/infrabox/datahub-operator/com.sap.datahub.linuxx86_64/installer-test-base:build_${INFRABOX_BUILD_NUMBER}",
        "resources": { "limits": { "cpu": 1, "memory": 1024 } },
        "depends_on": ["build-installer-test-base"]
    }

infrabox run build-installer-test-base creates datahub-operator_build-installer-test-base:latest, but not v2-registry.dhcp.wdf.sap.corp/infrabox/datahub-operator/com.sap.datahub.linuxx86_64/installer-test-base:build_local`.

infrabox run test-install cannot find its image, as the image was not tagged.