[FEATURE] Upgrade to using GPG Keys like everyone else.

docker login is a VERY complicated process just to keep our login info out of a clear text file. Even following the multi-step article to use a password manager results in an hour's worth of work or more to figure out why it can't find pass, and I still haven't figured out why it can't find it when I just installed and initialized it. (HINT: the following does NOT work.)

{
	"auths": {},
	"HttpHeaders": {
		"User-Agent": "Docker-Client/18.09.7 (linux)"
	},
	"credsStore": "pass"
}

So, let's look at the usual way things work.

1. GitHub authentication with git? pubkey pasted into the GitHub interface.
2. GitLab authentication? pubkey pasted into the GitLab interface.
3. Bitbucket authentication? pubkey pasted into the Bitbucket interface.
4. Docker authentication? Cleartext username and password unless you install some obscure software, configure that obscure software with GPG, and then hope you get lucky and Docker can find the obscure software it relies on.

Do we see a problem? Please make your client work like git does and allow devs to simply paste their pubkey into their docker.com account. It's ALWAYS best to keep to what people know so they don't have to learn something new just to use your product.

Start with the docker login entry point and the credential configuration shown in the issue, including the credsStore: pass setup. Done means defining and implementing a supported GPG/public-key authentication flow that avoids cleartext credentials without requiring the described password-manager configuration.