CLI: save "current" project and codeset as persistent state

[stefannica]

The CLI allows reading global options like URL, HTTP timeout and verbosity from a .fuseml/config.yaml configuration file. The same configuration file can be leveraged to store information that could be considered part of the CLI's state, such as:

• information about projects being used: project name, username, password
• information about codesets being used: codeset name, project name, location
• current project
• current codeset

Storing this information as persistent state allows the CLI to auto-fill some command parameters based on the "current" context, which makes it easier for CLI users to run repetitive commands, such as pushing codeset updates. The following context managing commands need to be implemented:

• fuseml project list - lists all available projects (currently only represented as gitea orgs)
• fuseml project set <project-name> - sets the "current" project
• fuseml codeset set <codeset-name> - sets the "current" codeset in the "current project"

Other commands related to codesets and projects should be modified so that they use the "current" project and "current" codeset if they are not explicitly supplied as arguments, as well as change the output to indicate if a displayed codeset is active or not.

[jsuchome]

What is interesting in this list of commands is that except for one (fuseml project list), they are all client only.

Just wondering if it makes sense to design an API..

[jsuchome]

And this

information about projects being used: project name, username, password

although it does not look like initially, is also client side only. Well at least partially. We can list orgs and associated users using our git client API, however not the passwords, these we'd need to store locally.