Refs. swh/infra/sysadm-environment#5005

Refs. swh/infra/sysadm-environment#5005

Update to upstream version '2.0.3'
with Debian dir 9c954df7ecec25bdc00a162461a6f48662e47dd8

Previously, in production, this would retrieve the configuration of the other backend as
those configurations are named the same.

Refs. swh/devel/swh-scrubber#4696

To avoid returning only the first one when multiple configuration with the same name
exists for different backend to scrub.

Refs. swh/devel/swh-scrubber#4696

Update to upstream version '2.0.2'
with Debian dir c102db69aa3b2576762b7cb434e9f9dae2957ef5

It's popping up after having run tests.

This was found while deploying the new version.

Update to upstream version '2.0.1'
with Debian dir d9a53205d4bce2ec9c70ca6a18fd9a674dab2637

With older click version (e.g. 7.0-1), the text wrapping can be different, resulting in
some docstring text included in this command list, so check we find the expected
commands instead [1] [2]

Refs. swh/infra/sysadm-environment#4992

[1] 'defined ...' is part of the first line of the docstring for the "init" subcommand.

```
10:21:42  E       AssertionError: assert ['init', 'defined...', 'journal', 'list', 'stalled', 'storage'] == ['init', 'journal', 'list', 'stalled', 'storage']
10:21:42  E         At index 1 diff: 'defined...' != 'journal'
10:21:42  E         Left contains one more item: 'storage'
10:21:42  E         Full diff:
10:21:42  E         - ['init', 'journal', 'list', 'stalled', 'storage']
10:21:42  E         + ['init', 'defined...', 'journal', 'list', 'stalled', 'storage']
10:21:42  E         ?         ++++++++++++++
```

[2] https://jenkins.softwareheritage.org/view/swh-debian%20(draft)/job/debian/job/packages/job/DSCRUB/job/gbp-buildpackage/31/console

Update to upstream version '2.0.0'
with Debian dir 5245db90af8684b0237d6b67104d3c5d85149f5d

This is needed to make it compatible with swh.core's db upgrade tooling:
the name of the configuration section is exptected to be the swh module.

Need to drop the index of the old checked_partition before recreating
the new one (with the same name); simplest way of doing this is cascade
droping the old checked_partition table before recreating the new index.

This is especially testing the fact the `--help` argument works when
running the `swh scrubber check --help` without any configuration file
set.

This flag reset the partitions identified as stalled by setting
start_date and end_date to NULL.

This should put these reset partition to be selected for checking by a
scrubber worker.

For a given configuration (hence sotrage, object_type and partition scheme)
list partitions that have a start_date but no end_date for a long enough
time.

By default, it will compute the delay for a partition to be considered as
stalled based on the 10 last partitions checked for the given
configuration.

A checker configuration must now be created before being
able to start a checker session. This configuration is stored in the
database and consist in a triplet

  (datastore, object_type, nb_partitions)

Once done, any number of checker can be started for this specific
checker configuration; each checher process will check partitions
one by one, using the status stored in the database to get the next
partition number to check on the next iteration.

This allows to dynamically adapt the number of checker processes.

For example, checking the shapshots splitting the hash space in 4096
partitions using 4 parallel workers could be like:

  $ export SWH_CONFIG_FILENAME=config.yml
  $ swh scrubber check init --object-type snapshot --nb-partitions 4096 --name cfg-snp
  Created configuration cfg-snp [3] for checking shapshot in postgresql storage

  $ for i in {1..4}; do (swh scrubber check storage cfg-snp &); done

This new table stores the "configuration" for a scrubber. A
configuration consists in a set of:

  (datastore, object_type, nb_partitions)

This comes with a migration script; WARNING: this script needs to be
checked before deployment on a productiion-sized big database. Any
activity on the database should be stopped before execution.

This is the first step of a series to make the scrubber easier to deploy
on elastic infrastructure.

It now needs types-click which is indeed a dependency of
swh.core[testing].

This allows overriding the JAVA_HOME to run cassandra with a different
java version (which also happens to be needed in CI, as we force usage
of an old java for cassandra through that envvar).

This avoids reinstalling tox all the time