Update to upstream version '1.8.1'
with Debian dir c37d81e5cce6e94d4368fbf955c5328b1e724d2e

Previous URL was starting with /api/1/vault/git_bare/ leading to a 404
while the correct one must start with /api/1/vault/git-bare/.

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

Update to upstream version '1.8.0'
with Debian dir 4f9af148a47c1148d7a8bc13d089833e634f4616

to more reasonable versions...

instead of creating it in the VaultBackend constructor: when configured
(with host and port), SMTP.connect() is immediately called, which makes
it mandatory to have the smtp server up and running to be able to create
the VaultBackend object (which makes it hard to run properly in an elastic
environment like docker or k8s).

This also removes the fallback to hardcoded 'localhost:25' smtp server;
if the smtp server is not configured or not reachable, the call to
_smtp_send() will fail logging the failure (both in logging and sentry).

Hash dicts are now prefered by swh-objstorage, in order to support
individual hash collisions.

Update to upstream version '1.7.2'
with Debian dir 6f80d43afd1d956ef58ef18adff5cc0330970d2e

because this later is not yet available on debian, and we do not use new
API features anyway in test_cookers.py

Should fix deb packaging.

Update to upstream version '1.7.1'
with Debian dir 8623141083e9f8f4a3d7e442f853e3f15ce4f3a9

'local' has been deprecated for a while.

This is not a runtime issue, because when the supplied mode is DentryPerms.symlink,
the target is only used passed to os.symlink, which does allow str too.

This can happen for various reasons, such as running the vault on
a mirror that is partially replayed

Update to upstream version '1.7.0'
with Debian dir 55101ca0f74aca2c6bb2f58149646f66ac51696a

objstorage.add() will change/remove its return value in a future version,
and we do not use it in the vault anyway.

This would be more usefully implemented by generating a (temporary) URL
for direct download of vault bundles from the azure bucket.

This fixes test build [1]

[1] https://jenkins.softwareheritage.org/view/swh%20master%20(draft)/job/DVAU/job/tests/1575/console

Related to T4305

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

to reduce test execution time a bit.
Keep test_git_bare_cooker using a postgresql backend, since it depends
on it (support for displayname).

Fix "more than one target found for cross-reference 'ObjectType'"
sphinx warning.

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

It was a class parameter from the swh.core.api.asynchronous.RPCServerApp which got
removed some time ago.

This is not defined in the swh.core.api.RPCServerApp.