It doesn't seems to be used anywhere, so Valentin in suggesting we drop
it instead in updating the dependencies to psycopg3.

Bump development tools: mypy, codespell, isort, ...

Move all tools configuration in pyproject.toml.

Remove no longer needed mypy overrides.

This is currently failing the checks [1]

[1] ```
09:31:14 <IRC Relay Bot> <s​whbot> icinga PROBLEM: service production Check
save-code-now subversion with type svn end-to-end on pergamon.softwareheritage.org is
CRITICAL: WARNING:swh.core.sentry:Sentry DSN not provided, events will not be
sent.SAVECODENOW CRITICAL - Save code now request for origin ('svn',
'https://svn.code.sf.net/p/zookeeper/code') took 11.83s and resulted in unsupported
status: accepted ; scheduled.
```

Refs. swh/infra/sysadm-environment#5399

Related to swh/meta#5075.

 The migration includes switching from the deprecated `data_files` to
`package_data` for deposit test data files.

For more information about the deprecation of `data_files`, see:
https://discuss.python.org/t/should-there-be-a-new-standard-for-installing-arbitrary-data-files/7853

For the Debian package, this means the following paths need to be used:
`/usr/lib/python3/dist-packages/swh/icinga_plugins/data/deposit/jesuisgpl.tgz` and
`/usr/lib/python3/dist-packages/swh/icinga_plugins/data/deposit/jesuisgpl.tgz.xml`

One reference is located in the following Puppet configuration:
https://gitlab.softwareheritage.org/swh/infra/puppet/puppet-swh-site/-/blob/production/data/common/common.yaml?ref_type=heads#L2737-2738

These are now rejected by swh-deposit

We currently have some icing alerts about 429 response [1]. The current code is not able
to deal with it. So, this reuses the retry decorator used in some other parts of the swh
base code to retry with a backoff when this occurs. This should fix the current
failures.

[1]
```
DEPOSIT CRITICAL - Getting the list of metadata returned code 429:
b'{"exception":"Throttled",​"reason":"Request was throttled. Expected available in 16
seconds."}'
```

Refs. swh/infra/sysadm-environment#5129

Convert README from markdown to ReST to make it embeddable in
docs/index.rst

This matches the production Azure-based deployment.

When using the Azure direct download functionality, the content type
gets reset to application/octet-stream, which is valid (albeit
suboptimal) for gzips.

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.

Valentin's fix for iteration of empty tarballs in the tarfile stdlib
module was merged and released in Python 3.11, so we need to handle that
case properly.

We only ever tested the single-origin case, and the CLI endpoint itself was
never adapted to work for multiple origins. Ensure that tests properly
support that case.

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).

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

This will allow distributing the 'load' across multiple origins;
so that https://github.com/rdicosmo/parmap does not end up
with thousands of visits (which makes swh-storage time out when
listing visits)

It fails once deployed on the server with a
DistributionNotFound(Requirement.parse('typing'), None) error

Related to T3129

Related to T3129

That hook can be frustrating as it can discard a long commit message
if it finds a typo in it so better removing it.

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

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

Due to test modules being copied in subdirectories of the
build directory by setuptools, it makes pytest fail by raising
ImportPathMismatchError exceptions when invoked from root
directory of the module.

So ignore the build folder to discover tests.

The '+' character in the 'after' was not escaped, so the server interpreted
it as a space.