Set up authentication modes

[lukeocodes]

This will explain how we plan to allow users to get started using the CLI

If the user wants to log in (this is the expected primary workflow);

• deepgram login will prompt the user to log in via the web using an OAuth2.0 device flow, and the API endpoints we create return a new API key (named "Automated CLI API Key for ") and should write to the config file.

If the user wants to manually set their API key into config;

• deepgram login --api_key=<your key> should write to the config file (should not read from the environment variable - as this is potentially confusing where the value might come from)

To support users who prefer environment driven credentials (and CI workflows) they should be able use parameters and environment variables.

• any command including --api_key=<your key> or a DEEPGRAM_API_KEY environment variable should just work

[lukeocodes]

Create a device flow client and server solution

1. client deepgram login will request a device code
2. community will create device code and return it
3. the device code is part of a URL that the CLI will prompt the end user to go to
4. the CLI will then start to poll (continuously request from) the community site for an api key in the background
5. the user completes the device code flow on the community site
6. the CLI then gets an api key and stores it as config