It makes more sense to query a range of partition ids with a fixed nb_partition
than a range of nb_partitions with a fix partition id

No migration because the next release will need to scrap the whole table
anyway.

GitLab will display the content of the README file when browsing the
repository. But in case the file is a symlink, it will display the
path pointed by the symlink. There is a 6 year old issue about this:
https://gitlab.com/gitlab-org/gitlab/-/issues/15093

We can workaround the issue by having the content at the root of the
repository and a symlink to this file in the `docs/` directory.

Tested in swh/devel/swh-py-template!27

Related to swh/meta#4960

Related to swh/meta#4959

This fixes python 3.7 support due to poetry, a dependency of isort, that
removed support for that Python version in a recent release.

This should avoid pointless reports to Sentry and Icinga on AdminShutdown
exceptions.

In order to remove warnings about /apidoc/*.rst files being included
multiple times in toc when building full swh documentation, prefer to
include module indices only when building standalone package documentation.

Related to T4496

- pre-commit from 4.1.0 to 4.3.0,
- codespell from 2.2.1 to 2.2.2,
- black from 22.3.0 to 22.10.0 and
- flake8 from 4.0.1 to 5.0.4. Also freeze flake8 dependencies.

Also change flake8's repo config to github (the gitlab mirror
being outdated).

For now this is a naive implementation, which does never rechecks.

For now, this does not use this information to deduplicate work.

It will be used by the storage_checker to 'remember' what ranges
it already checked recently across runs (and crashes), and to
monitor progress.

It will probably be useful to know what part of the check
takes the most time.

This will allow adding more tags easily in future commits

instead of (soon-to-be-deprecated) swh-core's postgresql_fact one.

This alleviates current locking issues where nothing gets written in production.

Related to T4228

Related to T4228

so migration tool can be used

Related to T4284

We migrated away from "local" a while back.

Related to T4228

Related to T4228

Related to T4228

The case where the datastore already exists was masked by @functools.lru_cache,
which persists for the lifetime of a test, causing the function not to be
actually called twice.

Related to T3922

black is considered stable since release 22.1.0 and the version
we are currently using is quite outdated and not compatible with
click 8.1.0, so it is time to bump it to its latest stable release.

Please note that E501 pycodestyle warning related to line length
is replaced by B950 one from flake8-bugbear as recommended by black.
https://black.readthedocs.io/en/stable/the_black_code_style/current_style.html#line-length

Related to T3922

This is heavily inspired by https://archive.softwareheritage.org/swh:1:cnt:c6dda7698c6aecf71f744e4e4c01bc3e115db880;origin=https://forge.softwareheritage.org/source/snippets.git;visit=swh:1:snp:c2e3170b9927f3d356e120546b00f5a9d25a224c;anchor=swh:1:rev:fa9e387ba5e3470b93a5c5a8773ed598ef03d211;path=/vlorentz/analyze_consistency_failures.py
but reorganized to the database instead of ad-hoc text and pickle files.

Currently, this only implements recovering from Git origins.

pytest-postgresql 3.1.3 and pytest-redis 2.4.0 added support for
pytest >= 7 so we can now drop the pytest pinning.