feat(loo-4729): api-key command

[notnmeyer]

• adds api-key subcommand for /api-key

➜ ENV=staging task -- api-key
task: [default] go run ./... api-key
Valid API key for team: nate-send4.l3s.email

• verify a key is legit before saving with login

# boo
➜ task -- login
task: [default] go run ./... login
Enter your API key:
Error: API key verification failed: invalid API key
Usage:
  loops login [flags]

Flags:
  -h, --help   help for login

exit status 1
task: Failed to run task "default": exit status 1

# yay
➜ task -- login
task: [default] go run ./... login
Enter your API key:
API key saved. Authenticated as team: nate-send4.l3s.email

• dev: the default task adds support for a dotfile file supplied with ENV, as seen above

[nalanj]

I think in general I prefer [noun] [verb] command patterns for this kind of thing. So like on auth I'd probably do auth login, auth logout, and auth status

[notnmeyer]

login was added in #1. can make a linear for it though, wont address it here. i was debating originally whether to have the top level be auth or not. 👍

[linear]

LOO-4729