fix: correctly load external config file

[dlouzan]

• external configuration files are properly handled
• transform verbose parameter in config file to a 'loglevel' integer
  that can be increased. uniformity in handling of verbose param
• add test cases

[dlouzan]

The current master is not able to load a configuration file passed with the -c option; I don't know if this is an upstream issue in commander, but the definition must use the .parent object, since it's defined on top of the command hierarchy.

Additionally, I made the handling of the verbose option more uniform, since each command was doing its own magic. One of the most recent changes made the verbosity a log level, so it is treated as an integer in code (1 is normal output, 2+ print debug information).

Lastly, the promise chain of each command will now show an error message if some bad exception happens. The current code will just swallow those and exit with an error status.

[pderaaij]

@djtarazona this one solves some problems with the current release. @dlouzan could you perhaps update the PR and resolve the conflicts?

[dlouzan]

@pderaaij I've just updated the PR. Only some issues with package lock.