GitLab

Merge everything to kamaki.clients

Remove multiple hierarchies of connection classes (== abandon support for
    alternative connection methods, e.g. for requests from pypi)

New connection classes are
- RequestManager
- ResponseManager
Semantics:
    RequestManager constructor commits a request without performing it
      but it performs all sanity checks for url, path, method and params
    RequestManager.perform will perform the commited request, if called
    ResponseManager constructor needs a RequestManager instance
    ResponseManager.(various properties)
        request is pooled from a ContextManagerPool (objpool) when needed.
        Results are cached and used as long as the ResponseManager instance
        is alive

Remove KamakiConnection/ResponseErrors, use ClientError wrapers for everything

Remove the connection livetest

TODO: Adjust unittests

- image compute group contains all Compute Image API commands, as oposed to
Plankton API commands.

- definition of a kamaki cli command slightly changed: a command with
subcommands can have a class without being a command itself, as long as it has
subcommands! Thus a subcommand group can be defined with docs and everything.

- image public is not image list (docs not updated yet)

Naming convention:

Actual functionality:

In package kamaki.clients.pkg there is class C containing a method M
Test it in a package kamaki.clients.pkg.test, with a class C + a method test_M
Command line run:
    python ${kamaki}/kamaki/clients/pkg/test.py C M
or
    python ${kamaki}/kamaki/clients/test.py C M

In package kamaki.clients there is a module mod containing a method M
Test it in a package kamaki.clients.mod, with a class Mod + a method test_M
Command line run:
    python ${kamaki}/kamaki/clients/mod/test.py Mod M
or
    python ${kamaki}/kamaki/clients/test.py Mod M

New dependency changes: progress is required, mock is optional
Changes are also documented

Onluy instatiation is tested so far

Methods tested so far: _matches, filter_in, filter_out