Update to upstream version '0.34.0'
with Debian dir d1489fbcf94a7c6a63233ae05f74d2de68f382bc

The default ONE level is used to keep the previous behaviour

Related to T3396

Update to upstream version '0.33.0'
with Debian dir 47fe726bda16965dd0e91bd305b768a9e6a855a4

Update to upstream version '0.32.0'
with Debian dir 5a82175111d28225036b7409520b88892fc695d2

This allows mypy to actually type-check calls to db methods.

This commit also fixes an issue found by mypy.

This will make it easier for users of swh-web to discover metadata
on a given SWHID, as you otherwise need to specify an authority to
fetch metadata.

We agreed a while ago they are IRIs, and we have some of them in the
postgresql database already.

Update to upstream version '0.31.0'
with Debian dir 04dce0f5260ddc7eeb91b361af1581a4c5dea4ec

This will be used by swh-web to allow downloading them
from a non-JSON endpoint.

All features work but snapshot_count_branches, because ScyllaDB does not
support user-defined aggregates yet.

Migration tests hang when run after the regular tests, but I can't
figure out why. This should not be an issue for now, as we won't run
Scylla tests on the CI.

Update to upstream version '0.30.1'
with Debian dir c5b4cee51262d233b57e30c0eadf8462f89b1de9

This will remove further deprecation warnings from the tests, especially the ones from
other modules depending on the storage's pytest-plugin.

This also fixes some edge case configuration for the backfill and the storage rpc
backend which would have been broken if we switched to that new name prior to this.

Related to b487a21f

pytest-xdist expects the parameters to be in the same order
in all processes.

Update to upstream version '0.30.0'
with Debian dir bd97b7a393ad1fb6f02d20bb88e4989e57e84535

Update to upstream version '0.29.1'
with Debian dir 7f0734a925b33f8b6d0c2fa241729777d3fbefd4

Update to upstream version '0.29.0'
with Debian dir b2c5f0460c76f4ec0b2043303c82c1a0eac711e2

Before this commit, the only way to get Content objects from their sha1_git
was to call content_find for each object.
This was obviously neither convenient nor efficient.

Using this endpoint to batch calls reduces the runtime of the git-bare
vault cooker by 30%.

It spares a join with the content table, which should hopefully make
the vault (and possibly other users) faster when they don't need this
join.