- blackify all the python files,
- enable black in pre-commit,
- add a black tox environment.

origin model no longer allows to have type.

Related to f533f62bbf114cfcc29f7c72307c4dfbe99cf048

Prior to this commit, we had the proper behavior of closing index when done
streaming. Unfortunately, this created too much gc on es nodes down the line.
So for now, we remove that behavior.

Note that this implies we need another cog that makes a pass once in a while on
indices to close.

Also, this has been running on production for 2 weeks now and no more gc issues
arose since then.

There is no reason to raise an error when a task type has already been
created and it enables to stop leaking psycopg2 IntegrityError exception
as part of the scheduler interface.

Required by swh-storage >= v0.0.172.

Using the `swh.storage.get_storage` function instead of calling directly the
class name.

This actually fixes the master ci build [1]

[1] https://jenkins.softwareheritage.org/job/DSCH/job/tests/743/console

Api wise, the `sentry_dsn` is expected to be passed as first parameter. Which
in the scheduler's case is not set yet. Forcing it to None for now.

This adds support for SWH_MAIN_PACKAGE to initialize sentry_sdk with a release.

Somehow, that messes other tests in the debian build.

Somehow, that fails in the debian build

For the moment, only 1 official es client exists

That actually make it consistent with the api

and test it

Celery silently eats errors happening in these functions.

Prior to this commit, we could list tasks whose started date was null. Now we
fallback on the scheduled task which is the next best date we have.