Update to upstream version '0.13.0'
with Debian dir 381261712ed7fa0561d14badf821880c2b4fc275

* Quote/unquote path
* Fix line parsing and serializing to properly handle None
* Fix error raised by check_visit/check_anchor

They were all very similar and only differ in what 'edge' cases they accept

by making them all derive from an abstract class.

Following the discussion on T3034, we decided to replace SWHID with
two or three classes:

* QualifiedSWHID to replace the existing SWHID (standard types + qualifiers)
* CoreSWHID, for "core SWHID" only (standard types + no qualifiers)
* ExtendedSWHID for internal use in Software Heritage (extra types + no qualifiers)

This commit adds the last one.

It also removes "ori" as a valid object type for CoreSWHID and
QualifiedSWHID, as it now only belongs in ExtendedSWHID.

It is cleaner, avoids warnings, and will be needed when introducing
ExtendedSWHID in a future commit.

And store their parsed values (CoreSWHID, tuple of ints, etc.) instead of string.

Following the discussion on T3034, we decided to replace SWHID with
two or three classes:

* QualifiedSWHID to replace the existing SWHID (standard types + qualifiers)
* CoreSWHID, for "core SWHID" only (standard types + no qualifiers)
* ExtendedSWHID for internal use in Software Heritage (extra types + no qualifiers)

This commit adds the second one

Following the discussion on T3034, we decided to replace SWHID with
two or three classes:

* QualifiedSWHID to replace the existing SWHID (standard types + qualifiers)
* CoreSWHID, for "core SWHID" only (standard types + no qualifiers)
* ExtendedSWHID for internal use in Software Heritage (extra types + no qualifiers)

Since migrating from SWHID will break existing code, this commit uses
the opportunity to modernize it a little, ie.:

* `keyword`-only constructor, to get rid of the hacky default values for
  `object_type` and `object_id`
* enum instead of strings for the object type
* `bytes` instead of an hex string for the object id
* rename `metadata` to `qualifiers`

Depending on the order in which tests are run, these tests may insert
lambdas with mocked blake2 functions in their closure to be inserted in
hashutil._blake2_hash_cache; causing all future tests to fail.

While this does not happen with the default order of tests, it does when
using pytest-xdist.

Update to upstream version '0.12.0'
with Debian dir fa312d034805923e43055018f760bb74d93020fa

so it's kept up to date when evolutions are made in the model and thus
preventing swh-journal and swh-model to be unecessarly coupled.

Related to T2970.

Update to upstream version '0.11.0'
with Debian dir ad60fcf7e9e7237e4c2e6dd0680004d3379e7ab9

Related to T2961

Update to upstream version '0.10.0'
with Debian dir 3349854b23ac224df660256b72722b90d897af10

The optional nature of the type will allow to avoid migrating the
(db) data model right now then we can have this type field in kafka
messages in the origin-visit-status topic

Related to T2443

They were mixed in with snapshot tests.

test_identifiers: Make sure that {directory,revision,release,snapshot}_identifier() doesn't just return a value from the dict.

For example, before this commit, you could replace the code of
revision_identifier() with this:

def release_identifier(release):
    return release.get("id", b"")

and all tests would still pass.