for now, managing the dbversion table (storing the db schema upgrade
history) is partially the responsibility of the swh modules implementing
a datastore (swh-storage etc.), and the actual swh module was not stored
in the database.

This adds support for both the dbversion and dbmodule tables management
in swh.core.db.

The `swh db init` command now creates both these tables and initialize
their values if possible.
For this, it introduces a new common "API" for swh.core.db based datastores:

- a swh module implementing a datastore is expected to have a
  `get_datastore` function in its top namespace; this function is
  typically the actual `get_storage`, `get_scheduler` etc. functions
- this factory function is expected to use the "postgresql" cls for the
  datastore based on swh.core.db,
- the datastore instance (eg. instance of the swh.storage.postgresql.Storage
  class) is expected to have a `get_current_version()` method (returning
  an int).

This revision also provides a new `swh db version` command displaying
the current (code) version (if available), the db version (possibly the whole
version history) and flavor (if any) for the datastore given as argument.

It should be backward compatible with existing swh datastore modules (i.e.
not yet adapted to this new API).

will be used to implement several test scenarios in following commits.
Also rename existing sql scripts with a "legit" numbering scheme.

Roughly, the idea is that http queries are transformed into file queries within
http context. If found, the data file is served or not (404). This translates
into query response so that the code can actually complete as usual.

For technical reasons the pytest plugin is in a dedicated non-swh module. This
is actually required for the pytest plugin loading mecanism to work without
hijacking the loading of swh packages. See [1] for more details.

[1] https://github.com/pytest-dev/pytest/issues/2042

related to T1265.