Update DinD image to make it possible to configure HTTP proxies

[cofyc]

What problem does this PR solve?

fixes #461

What is changed and how it works?

Check List

Tests

Manual test (add detailed scripts or steps below)

configure http proxies in docker config.json

    "proxies": {
        "default": {
            "httpProxy": "http://192.168.90.1:1087",
            "httpsProxy": "http://192.168.90.1:1087",
            "noProxy": ".svc,.local,127.0.0.1,0,1,2,3,4,5,6,7,8,9"
        }   
    }

propagate http proxies to dind containers

export DIND_PROPAGATE_HTTP_PROXY=true
manifests/local-dind/dind-cluster-v1.12.sh up

Does this PR introduce a user-facing change?:

NONE

[cofyc]

"noProxy": ".svc,.local,127.0.0.1,0,1,2,3,4,5,6,7,8,9"

This is used to whitelist all internal k8s domains, local registry (e.g. http://127.0.0.1:5000) and other IP addresses.

[AstroProfundis]

Do we need to add instructions to the doc?

[cofyc]

@AstroProfundis sure, I'd like to add this as an alternative option to KUBE_REPO_PREFIX because it works for all blocked images.

[cofyc]

@onlymellb I've updated DinD image and tested it on Linux successfully.

[onlymellb]

LGTM

[cofyc]

@weekface @onlymellb
I've rebased on the latest master. PTAL again.

[cofyc]

/run-e2e-tests

[weekface]

This pr needs to add a release note? @cofyc