Send auth credentials to the Docker socket if Docker config file is mounted

### Current Status

Currently, if a Docker config file were to be mounted to the peer containers to either `/root/.dockercfg` or `/root/.docker/config.json` with credentials for a private repository, `fabric-peer` won't send the configured credentials to the socket. This becomes an issue when the peer tries to pull the chaincode build environments (`fabric-baseos`, etc.) from a private repository.

### Expected

If a Docker config file has been mounted to the peer, the peer should check if auth credentials are provided in the config file and send them to the socket.

### Solution

_No response_

### Please let us know if you plan to work on this.

Yes!

Start at the fabric-peer entry points that communicate with the Docker socket and trace how mounted Docker config files are detected. Check the existing image-pull and authentication flow, then verify that credentials from either stated config path are sent when pulling private chaincode build environments.

Written by the indexing model from the issue text.