Update to upstream version '2.1.0'
with Debian dir 6b5419fe87be223d70c9630dfdc5de683ccac7f3

this object aims at being able to keep in the SWH Archive an
  SWHID <-> External object ID
map, e.g. to be able to keep track of Mercurial ids so the Mercurial
loader can be made more efficient.

Related to T2849.

was modifying the dict given as argument.

Update to upstream version '2.0.0'
with Debian dir 40768420e535abdbc97e85502bba4b26414a1ea8

Update to upstream version '1.0.1'
with Debian dir 1d3154e2d3c122633977ccf26667b87beed97a02

The rounding algorithm wasn't specified

Serializing as ISO8601 makes the hash brittle, because the database may
change the timezone silently and/or lose precision in the microseconds.

As we do not need precise timestamp, using an integer is good enough,
and is consistant with the git format.

The manifest also does not need to contain a timezone, as it only
represents the timezone of the system that fetched this metadata,
which is useless data.

So that they can be properly deduplicated and referenced.

This will be used to compute an intrisic identifier for RawExtrinsicMetadata;
which can be used for deduplication and refering to it like any other sha1_git
instead of needed to use a tuple of its fields.

Other packages don't use it anymore.

Update to upstream version '1.0.0'
with Debian dir b4105a4c2fba097e2c03fbbbcfecf5612e3885d6

This is a useful shorthand when generating SWHIDs in tests.

SWHID is deprecated; and CoreSWHID does not support qualifiers at all,
so RawExtrinsicMetadata no longer needs to check there are no qualifiers.

ExtendedSWHID can identify either a software artifact or an origin,
so we no longer need Union[SWHID, str].

Therefore, we no longer need the 'type' attribute, as it was only
used to tell when the target is a SWHID and when it's an origin URL.

It can be handy as a shortcut to build SWHID objects.

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.