we want the root logger configured there, not the cli one.

to make sure each extra setup dependencies are ok.
This requires to move test files in its related subpackage.

Warning: this may break swh packages that depends on swh.core which have
not been updated to swh.core 0.0.60.

Note that for now, the main requirements.txt still contains all the
dependencies for backward compatibility reasons.
This will have to be fixed once all packages that depends on swh.core
have been updated.

closes T1678.

This allows to declare click-based subcommands using the setuptools'
entry point "swh.cli.subcommands".

The main "swh" command group does only handle the "--log-level" option.

Also extract the db-init command in a dedicated submodule and ensure both
  swh db-init
and
  swh-db-init
work.

Related to T1671.

so that 3rd-party ones are in a dedicated 'section' as described in PEP8

  https://www.python.org/dev/peps/pep-0008/#id23

So they gracefully release the connection on error instead
of relying on reference-counting to call the Db's `__del__`
(which does not happen in Hypothesis tests) because a ref
to it is kept via the traceback object.

using an incremented counter, instead of pushing an inacurrate timing
data (if calling the encapsulated function raises an exception).

pushing streamed content should not imply the result is streamed.

- add a default implementation of the exception class
- make the exception class a class attribute of SWHRemoteAPI that can be
  overloaded at instanciation time by the api_exception named argument
- so the api_exception positional argument of SWHRemoteAPI becomes a named
  argument

WARNING: This later point does break compatibility for any use of this class
not using named arguments when instanciating it. Fortunately, as far as I
know, every swh packages does use named argument when instanciating this
class, so this should not break anything.

- ensure we do accept **kwargs so any super().__init__(**kwargs) from an
  unexpected MRO path in an indecent maze of multi-inheritance will not crash
- do not call super().__init__(); it is either useless (most probably,
  super() is object in this context) or silently ignore passed kwargs that
  super() (when it's not object) may have been able to understand...

Long story short, kwargs handling in multi-inheritance __init__ methods is
a mess.

- merge raw_post and row_get in a unique raw_verb method,
- merge post_stream() and post() as a unique post(); post_strean is then a
  call to post with the 'stream' parameter set,
- merge get_stream() and get() the same.

so the pytest-postgresql fixture works as expected on non C locale systems.

we almost never return text/plain or text/html, so json is a better default
value.

for debugging purpose.

this will take precedence over the implicit config file scheme.

Related to T1410 and T826

`entry_to_bytes` and its friends were called many times (eg.
entry_to_bytes alone was called 40k times while indexing 500
origins with the metadata indexer), and its use of `isinstance`
used a non-negligible amount of CPU time.

Instead of using `*_to_bytes` function as post-processing on
all bits of data returned by postgresql, this patch tells psycopg2
to use a new `typecast_bytea` function when needed (in `adapt_conn`).
This function deffers the decoding work to psycopg2, which returns a
`memoryview`, which is turned into `bytes`.

to keep the copy_to API bw compatible.

This needs tests!

so thath it does not fail if no payload at all is provided in the request,
eg. for an endpoint which really is (or at least should be) a simple GET...

just to make our life a bit easier...

so one can use this method with default values for some columns. This is used
for example in scheduler.

it is not a 'private' method. Add a _cursor alias for bw compat.