use stored API key instead of CONNECT_API_KEY env var when deploying content to saved Connect server

[dethmasque]

When CONNECT_API_KEY is set and you attempt to deploy content to a Connect server using -n/--name instead of -s/--server and -k/--api-key the command fails with Error: -n/--name cannot be specified in conjunction with options -k/--api-key.

We should use the stored API key instead of taking the CONNECT_API_KEY environment variable into account.

Ex:

questionsleep$ export CONNECT_API_KEY=awwyee
questionsleep$ rsconnect deploy streamlit -v --name dogfood --entrypoint app.py ~/Git/rsc-hello-world-content/python3/python-streamlit/
    Warning: the existing manifest.json file will not be used or considered.
Error: -n/--name cannot be specified in conjunction with options -k/--api-key

Unsetting CONNECT_API_KEY allows deployment to proceed:

questionsleep$ unset CONNECT_API_KEY
questionsleep$ rsconnect deploy streamlit -v --name dogfood --entrypoint app.py ~/Git/rsc-hello-world-content/python3/python-streamlit/
    Warning: the existing manifest.json file will not be used or considered.
Validating server... 	[OK]
Validating app mode... 	[OK]
Making bundle ... 	[OK]
Deploying bundle ... 	[OK]
Saving deployed information... 	[OK]
Building Streamlit application...

Some verbosity improvements would be helpful as well (e.g. Using stored account key... Using CONNECT_API_KEY environment variable... etc.) . -v doesn't glean any additional information when deploying.