GitLab

Refs: #3728

Refs: #3716

Behavior After This:
kamaki -XXX -YY ... parses -XXX -YY
If not recognized: syntax error
If recognized, group them into shell args (e.g. -h) and command args (e.g. -d)
Whenever a command is run in this shell instance, apply the command args

Practically, users may pass the -d or -v args to the shell and enjoy streaming
debug or verbosity logs, without having to pass -d or -v args on each command

Refs: #3663

A command group that is declared in the config file is not supported
by valid command specification code or the specification code is not
pointed at by <command>.cli configure variable

use logging for getting the loggers

This caused warnings about preset variables

refs: #3715
Logger settings are not aborted and will be restored at deactivation

Also, remove all logger creation functionality from kamaki.clients
A file or stream logger should be created an the kamaki.clients caller side
In this case, the caller is kamaki.cli
Kamaki.cli should handle where and how the loggers will output. Kamaki.clients
will log as __name__ and the two extras: kamaki.clients.send/recv

An external app can now import kamaki and create a logger named "kamaki" and
this will log whatever kamaki is logging. The external app will handle loggers
as they wish.

Unsolved bug: redudant info in logfile

Refs: bug #3708

containerlimit set -h will tell users to use 0 for unlimited
containerlimit get will print "unlimited" if received a 0 value

Container limit 0 means "unlimited"

The connection between kamaki request attempt and httplib response was
logged, but the connection between httplib response and kamaki response
managment was not logged.

One default: ~/.kamaki.log
User can use a custom: kamaki config set log_file <custom log file>