Use environment variables as substitution for passing in --url and --access-token

Problem Description
We use jfrog-cli in our Jenkins pipeline. However, it appears that now we can bypass adding the ~/jfrog/*.conf configuration by adding the parameters --url <artifactory> and --access-token <token> to a large subset of jfrog-cli commands.

Solution
We'd like to be able to use jfrog-cli without using the extra command line parameters (since not every command needs them) via the environment. For example, it would be very handy if we can use them via

• JFROG_CLI_ACCESS_TOKEN="SSD(S))@)@@>.."
• JFROG_CLI_URL="https://artifactory.failsafe.com"

Here, it would be helpful that the jfrog-cli command itself understand that the URL is https://artifactory.failsafe.com and appends "artifactory" where necessary (e.g. https://artifactory.failsafe.com/artifactory.

This would be particularly helpful in a docker environment where passing in credentials can't be done via stdin, and using the command line argument is "insecure" if not done right

Alternatives
We've been able to use it via the command line, but I can't pass it a fixed set of parameters that works for every command.

Start by tracing how jfrog-cli commands currently consume --url and --access-token, and how command-line values interact with configuration. Define the environment-variable precedence and the requested Artifactory URL normalization, then verify representative commands work without those flags while existing flag and configuration behavior remains unchanged.