pulp config refuses to work in case the config file is not valid

[thmo]

When the existing config file is not valid, not even editing the config file works:

$ pulp config edit              
Usage: pulp [OPTIONS] COMMAND [ARGS]...
Try 'pulp --help' for help.

Error: Invalid value for '--format': invalid choice: jsonn. (choose from json, yaml, none)

In this special case, pulp --format=json config edit helps.

In general though, if the config file fails to parse, it would be nice to get a warning and still be able to run the pulp config ... commands.

[mdellweg]

I think, this means we need a way to verify the config (beyond the fact that it's valid toml) and reject using it with a warning.
Issuing an error blocks the config commands, and providing a way to not use a config file is no better than the workaround described in the issue.
Maybe we can ask the user for confirmation before continuing without the config.