This returned a Tuple[OriginVisit, OriginVisitStatus] which is no longer needed as now
OriginVisitStatus held the type information now.

Explains:

* when to use swh-web instead
* that `get_storage` should always be used to instantiate the storage
* `StorageInterface`
* model objects
* pagination
* backends

If the type is not present on an origin_visit_status, it
should be computed from the origin_visit.
There were some methods which only return the origin_visit_status
value. It breaks the webapp mangling the type to empty value on
the search result page.

Related to T3001

Related to T2961

useful when the type is not yet populated in the database

Related to T2966

(!) A new database upgrade is needed (165.sql) for postgresql backend

Related to T2964

Since 209de5db, it was failing because of:
TypeError("content_add() got an unexpected keyword argument 'db'")

Depends on D4848
Related to T2443

This allows to enforce a specific version of java to be used. For
example, since cassandra seems not to support java 14 yet, this allows
to run tests on bullseye:

  JAVA_HOME=/usr/lib/jvm/java-11-openjdk-amd64/ pytest swh

hypothesis 6 upgraded a warning into an error: now raises a FailedHealthCheck
when using a pytest fixture with a @given generative test set.

See https://hypothesis.readthedocs.io/en/latest/healthchecks.html

prevent being fooled by a missing '\n'.

As it's exposed through the swh.storage.pytest_plugin itself used by other swh
modules, this needs to be declared to avoid other swh module build failures.

Related to T2746

requirements-swh.txt already declares the swh.core[db] dependency which
transitively pulls it.

Related to T2746

The previous code would nullify all non-null branches, and try to create a
SnapshotBranch out of null branches.

As this happens for about 50 revisions in the archive.

This module's use of write_addition predated the introduction of reliable
writing in swh.journal; Since this introduction, the backfiller has been
flushing the kafka writer after writing each single object, leading to a 3x
measured slowdown on backfilling contents.

as this happens quite often and isn't an error.

migrate_extrinsic_metadata: add support for guessing the origin of more PyPI packages from filenames.

Because it makes a lot of get requests and doesn't handle failures,
it crashed often.

The metadata migration script kept crashing otherwise.

The next version of swh-journal will remove the default value.

It complicates the signature and the code, and we don't have any use
for it currently.

1. rename branch_info to last_branch
2. exclude the last_branch from 'branches', so that:
   a) it never needs to contain a None value, so we don't need a cast
   b) no need for slicing

Consistently with the new name for this attribute in swh.model 0.7.2.

For consistency with swh.model v0.7.2, to prepare for the addition of
an (intrinsic) id field to RawExtrinsicMetadata objects.

For consistency with swh.model v0.7.2, to prepare for the addition of
an (intrinsic) id field to RawExtrinsicMetadata objects.

Related to T2734

To match the new behavior of package loaders.

The old attribute was deprecated in swh.model 0.7.2

swh.model.model.ModelObject.compute_hash was changed to a method instead of a
staticmethod.

migrate_extrinsic_metadata: Make pypi_origin_from_filename fix project names when possible using PyPI's API.

Instead of bloating handle_row, which is already way too long.