Add support to resolve artifacts from private docker registry about spring-cloud-deployer-local HOT 2 OPEN

Given that The local deployer uses the regular docker command, I believe there is nothing that can/should be done for this to work.
If the user has successfully authenticated against said repository (using docker login my.jfrog.io) then everything should just work.

Background reading: https://docs.docker.com/registry/deploying/

from spring-cloud-deployer-local.

Note that the format of authentication for the particular repository may be a bit peculiar, which may explain issues the original user may have.
For example, reading the doc about bintray: https://bintray.com/docs/usermanual/formats/formats_dockerrepositories.html

But again, I believe there is nothing we have to do at the SCDF level. All matters of authentication (even k8s pullSecret, which have nothing to do here) require that authentication is first done locally in docker. Once this is done, then things should "just work" given we're using the docker client

from spring-cloud-deployer-local.