Update to upstream version '2.2.0'
with Debian dir 11b2ea1d87056f6ef6e31f1af6bf8e1736de8d91

It now requires a swh-graph server running or connection errors appear.

Use swh-graph NaiveClient to avoid spawning a real graph server during
the tests.

As well as a command to list partitions being checked.

For example:

```
$ swh scrubber check stats snapshot_16 -j
{
  "config": {
    "name": "snapshot_16",
    "datastore": {
      "package": "storage",
      "cls": "postgresql",
      "instance": "postgresql:///?service=swh-storage"
    },
    "object_type": "snapshot",
    "nb_partitions": 65536,
    "check_hashes": true,
    "check_references": true
  },
  "min_duration": 0.002196,
  "max_duration": 0.107398,
  "avg_duration": 0.005969,
  "checked_partition": 65536,
  "running_partition": 0,
  "missing_object": 0,
  "missing_object_reference": 0,
  "corrupt_object": 0
}

$ swh scrubber check running cfg1

Running partitions for cfg1 [id=1, type=snapshot]:
0:	running since today (20 minutes)

```

Update to upstream version '2.1.0'
with Debian dir 3c4fd0e10e56250c835a4340037f123e483503c0

init` command

These flags allow to configure a checking session including only one of
the 2 possible checks (hash computation and reference validation).

Which allows to remove the dependency on types-pyyaml in [testing]
extra.

These tables used to reference the datastore the invalid/missing object
was found in, but not keeping the config entry, i.e. the checking session
during wich the invalid/missing object was found, which can be an issue
when more than one checking session is executed on a given datastore.

This replaces the `datastore` field of tables `corrupt_object`,
`missing_object` and `missing_object_reference` tables by `config_id`.

Adapt all the code accordingly.

Note that it changes a bit the cli usage: the kafka checker now needs
a config entry, thus a kafka checking session can ony target a given
object type (i.e. one kafka topic),

The migration script will fill the config_id column for corrupt_object
using the check_config entry that matches the oject_type (of
corrupt_object) and datastore. For missing_object and
missing_object_reference, it will use this later table to idenify the
check_config entry corresponding object type for the reference_id and
datastore, since it is a checking session on this object type that will
generate a missing object entry (which is generaaly not of the same
type). For the missing_object table, the config_id will use the one
extracted from the missing_object_reference (joining on the missing_id
column).

Note that the migration script will fail if there are rows in one
of these tables for which there exists more than one possible
config_entry (i.e. with the same object_type and datastore).

was missing the flake8-bugbear dependency, making effectively the
line-too-long check disabled.

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.