--env-token-name flag is defaulted to `access_token`, its not possible to set it to `none` which would activate different jinja template features

[ITJamie]

Describe the bug --env-token-name flag is defaulted to access_token, its not possible to set it to none which would activate different jinja template features

To Reproduce attempt to set --env-token-name to none. its not possible via the cli.

Expected behavior ability to set --env-token-name to none thus using the alternative token setup method in apiconfig.jinja2 which would allow passing in the authtoken instead of expecting it to be set at the environment level

Additional context if "false" or "none" are passed to --env-token-name it should override the value to none

[mschmitzer]

Ran into the same issue. Simply defaulting the --env-token-name option to None would be good, IMO. I can file a PR if that helps, but it seems silly for a single-line change :smile: