Related to T3578

Update to upstream version '0.37.0'
with Debian dir 304ad56e032c6f722cf702178ece7d62e3dcef12

This impacts both the `extid_get_from_extid` and `extid_get_from_target` endpoints.

Whe extid_version/extid_type are not provided, this keeps the existing behavior of
returning all extids matching.

Related to T3567

All packages now pass

This should make it run up to 100 times faster, even on average directories.

Instead of fetching them one-by-one, with the very high latency this entails.

This is preliminary work to make `directory_ls` less painfully slow.

And fall back to concurrent insertion.

By reusing the 'steady state' main statement (which is quite large)
across calls.

This adds a new config option for the cassandra backend,
'directory_entries_insert_algo', with three possible values:

* 'one-per-one' is the default, and preserves the current naive behavior
* 'concurrent' and 'batch' are attempts at being more efficient

This will be used as a second pass on objects that failed with
older versions of the script.

They were inaccurate and a performance bottleneck.

We can/should use swh-counters instead, now.

resulting in OriginVisitStatus trying to put a snapshot id in the
metadata field

Related to T3539

Related to T3517

It will be used in the Cassandra experiment.

Currently we use the built-in counters of the Cassandra backend; but in
addition to being inaccurate, they seem to be a bottleneck.

This proxy will be a lightweight solution for counting object insertion,
without needing to run Kafka on the test cluster.

Update to upstream version '0.36.0'
with Debian dir 179c1ad6d3ce02e0f64d5944d38e3e3d48e86d89

It was unclear this actually worked; I had to write this test to realize
the code wasn't buggy.

Also replaced a conditional that is always False (because Cassandra
always returns results in the order of the clustering key) with an
assertion, so the code is less confusing.

When called by a replayer, the visit.visit field is set; but
origin.next_visit_id was never incremented, so on the next loader
run, the visit id would be 1 even if there is already a visit
with that id.

Instead of calling content_find() for each object, which needs to make
two queries for each.

Given the latency of Cassandra queries, this should be a significant
speed-up (possibly up to 100 times faster, as this is the value of
PARTITION_KEY_RESTRICTION_MAX_SIZE).

This also changes the schema, because CQL does not allow doing `IN`
queries on compound partition keys.

Related to T3485

Update to upstream version '0.35.1'
with Debian dir 313295a88c0c4c4f7c924c7c36bea4c310f2cbca

Update to upstream version '0.35.0'
with Debian dir 6ad84ab1c5fb66c4ead922e0b750291db31def2f

This fields allows having multiple version of the ExtID -> SWHID
mapping, for instance when the implementation of a loader changes in a
backwards-incompatible way.

For now, we don't change the API used to query or store ExtIDs. When
querying for the SWHIDs corresponding to a given external objects, all
versions are returned, and the client is expected to do the filtering.

Update to upstream version '0.34.0'
with Debian dir d1489fbcf94a7c6a63233ae05f74d2de68f382bc