it's not used by swh.storage.

Now that we have packaged tenacity 6.2 for debian buster and use it
in production, we can remove the workarounds to support tenacity < 5.

The idea is that we check the BaseModel validity at journal
deserialization time so that we still have access to the raw object from
kafka for complete reporting (object id plus raw message from kafka).

This uses a new ModelObjectDeserializer class that is responsible for
deserializing the kafka message (still using kafka_to_value) then
immediately create the BaseModel object from that dict. Its `convert`
method is then passed as `value_deserializer` argument of the
`JournalClient`.

Then, for each deserialized object from kafka, if it's a HashableObject,
check its validity by comparing the computed hash with its id.

If it's invalid, report the error in logs, and if configured, register the
invalid object in via the `reporter` callback.

In the cli code, a `Redis.set()` is used a such a callback (if configured).
So it simply stores invalid objects using the object id a key (typically its
swhid), and the raw kafka message value as value.

Related to T3693.

We stopped using it months ago.

All methods of CqlRunner were decorated, which prevented mypy from doing
anything useful.

As I finally found a way to type the decorator (using
mypy_extensions.NamedArg), I can finally make mypy aware of the methods' types.

This commit (as well as all three of the last commits) also fixes issues found
by mypy thanks to this.

Instead of untyped dictionaries.

This makes snapshot_get longer and duplicates its code across backends;
but snapshot_get should be removed soon.

Related: T645

This endpoint is not really useful since the origin_add() can be used
instead.

Using a single API endpoint would also make the API a bit more consistant
(most other endpoints only provide a xxx_add endpoint) ; having a single
endpoint per object_type make is enough and make the whole API simpler.

This makes its api consistent with other add endpoints.

This is preparatory work towards removing origin-visit-upsert.

Related to T2310

The bug that affected us in 3.21 is resolved
( https://datastax-oss.atlassian.net/browse/PYTHON-1205 ),
so we can now use v3.22 to get wheels.

Which is a maintained fork of retry

The head version of the objstorage migrated. Thus the archiver tests
broke locally.

The test code was fixed to make the local tests pass with the actual
head version of the objstorage.

But we did not deploy the new objstorage yet, thus the archiver tests
break during the packaging phase (of any swh.storage.* package).

This commit is a temporary fix to make everyone happy (since we do
need to package other storage version for example).

This needs to be reverted as soon as we bump the dependency to the new
objstorage (> 0.17).

Related f681f83c
Related b4dfe06f
Related 08827dc5
Related D205

Related T529

Closes T646

The check_config method allows a dynamic check of the configuration for
a running storage. We can make sure that we have proper permissions on
the object storage as well as the database before running things.

If you want the archiver to have cloud abilities, install the
package python3-swh.objstorage.cloud on the server as well.

Actions storage:
- Open cache_content_get to retrieve contents in cache
- sql/upgrades/080: Add stored procedure to read contents from cache

Actions archiver:
- d/control: Add dependency to archiver on python3-swh.objstorage.cloud
- Renamed Archiver(Director|Worker) to
ArchiverWithRetentionPolicy(Director|Worker)
- Add ArchiverToBackend(Director|Worker)
- Add new celery task dedicated for new workers
- Update docstring details

Related T555

Closes T460

Closes T404