Description of problem:
   
    On OCP4 cluster installed on restricted network, "oc adm release info --registry-config" keeps trying to access "quay.io" instead of mirror registry.
     
    Version-Release number of selected component (if applicable):
     
    My reproduce environment is 4.3
    $ oc version
    Client Version: openshift-clients-4.3.0-201910250623-88-g6a937dfe
    Kubernetes Version: v1.11.0+d4cacc0
     
    The customer's environment is 4.2.
     
    How reproducible:
     
    Steps to Reproduce:
    1.
    $ vi /var/lib/kubelet/config.json
    $ cat  /var/lib/kubelet/config.json
    {"auths":{"https://index.docker.io/v1/":{"auth":"YWRfbGzhcGU6R2labnRib21ifTE=","email":"user"}}}
    $ /var/lib/kubelet/config.json | jq
    {
      "auths": {
        "https://index.docker.io/v1/": {
          "auth": "YWRfbGzhcGU6R2labnRib21ifTE=",
          "email": "user"
        }
      }
    }
     
    2.
    $ oc adm release info  --registry-config='/var/lib/kubelet/config.json' --loglevel=6
     
    Actual results:
    It did not access the mirror registry regardless of "--registry-config" option value.
     
    Expected results:
    It should access the mirror registry.
     
    Additional info:
    I attach two commands results.
    $ oc adm release info  --registry-config='/var/lib/kubelet/config.json' --loglevel=6
    $ oc adm release info  --loglevel=6