Introducing project subcommand

[davidzhao]

Instead of having to pass in connection details or rely on a fixed set of environment variables, the project subcommand would save multiple connetion details in ~/.livekit/cli-config.yaml.

The design of the CLI takes inspiration from kubectl, where all commands are able to take in a --project flag and automatically use details from that project.

listing projects

% ./bin/livekit-cli project list
+------------+-----------------------------+--------------------------+---------+
|    NAME    |             URL             |         API KEY          | DEFAULT |
+------------+-----------------------------+--------------------------+---------+
| my-server  | https://my-server.host.com  | API012348rquKztZEoZJVabc | true    |
| local      | http://localhost:7880       | devkey                   | false   |
+------------+-----------------------------+--------------------------+---------+

adding project

% ./bin/livekit-cli project add 
Enter project details
✔ URL: http://myhost.com█
✗ API Key: █

setting as default

% ./bin/livekit-cli project set-default local
Saved CLI config to /Users/davidzhao/.livekit/cli-config.yaml
Default project set to local

[matkam]

LG!

It could be nice to be able to add projects without a prompt:

./bin/livekit-cli project add --name xxx --url xxx --api-key xxx --api-secret xxx

[davidzhao]

./bin/livekit-cli project add --name xxx --url xxx --api-key xxx --api-secret xxx

good idea, makes it faster for advanced users.