Improve docker login experience with Artifactory registry

[scott-hpe]

Is your feature request related to a problem? Please describe.
Today, jfrog-cli will wrap a few docker cli commands, including jf docker push and jf docker pull. Notably, these commands will automatically log into the registry using the Artifactory creds stored by the jfrog-cli.

The feature request is to consider supporting the jf docker login command or make use of docker credential helpers.

Describe the solution you'd like to see
When working with Artifactory docker registries, users are often prompted to first login with docker login. Even when jfrog-cli is setup, this becomes a multiple step process of looking up the Artifactory credentials and then running docker login. The problem scope increases when using short lived tokens and SSO.

To improve developer experience and streamline the use of Artifactory registries, adding support for jf docker login would provide a streamlined developer experience when working with Artifactory. The expectation is that the jfrog-cli would be responsible for handling token refresh and authenticating to the Artifactory docker registry with minimal developer interaction or interruption to the developer workflow.

Describe alternatives you've considered
As an alternative, making the jfrog-cli a docker credential helper could be considered.

Additional context
The main goal here is to streamline the docker login experience when working with Artifactory registries. As DevOps teams migrate away from long lived passwords and towards tokens, refreshable tokens, and SSO login methods, we want to see an improved experience for Artifactory docker registry login that does not require the developer to look up credentials or manually refresh short lived tokens.