Update to upstream version '3.0.0'
with Debian dir bb9cc036ee04c90a51f9c99a8ecabec167da2dc1

For consistency, as the classes are now in swhids.py

+ raise warnings

1. Add a warning
2. Move identifier/manifest documentation to git_objects.py
3. Remove all imports of that module.

Motivation:

* SWHID classes were moved to swhids.py
* manifest computation functions were moved to git_objects.py
* Only reexports and trivial wrappers of model.py remain

They are not used anywhere.

Since they are used by the vault for non-identifier-related stuff,
I think it makes sense to move them to a new module.

identifiers.py is now an empty shell, as all its features were moved to
other modules and it only contains reexports and backward-compat
functions. Therefore, it should be considered deprecated from now on.

Refactor identifiers & model to make *_git_object() functions work on model classes instead of dicts

Since we now use these classes everywhere, computing hashes required
using to_dict() just to compute identifiers, which can be a performance
bottleneck in code computing many checksums.

A future commit will make identifier computation use the attrs classes,
which are strict about what they accept.

identifiers.py initially worked only on bare sha1_git.

I chose to add the SWHID classes in that module because
of the name, but the SWHID code didn't actually interact
with the other functions in the module, so it now feels
out of place to me.

We're about to have a Bazaar loader

Update to upstream version '2.9.0'
with Debian dir 678de30f3ce51fa5b29bcb9eb4b319cf3194cc1d

This class is a mixin that only works with classes that define
this attribute, so it makes sense to declare it.

It also allows generic functions (that take a HashableObject
parameter) to access it without 'type: ignore'.

Update to upstream version '2.8.0'
with Debian dir 2a0eb3550f469cd69a7d41680ae675ccd875ad66

Update to upstream version '2.7.0'
with Debian dir 6b15a8156e4b0b1122df1ae88f663dd3f0956acb

This allows distinguishing multiple potential versions of the mapping
between external objects and their counterparts archived in Software
Heritage, for instance when a loader has a backwards-incompatible change
that should result in objects being loaded again.

The field defaults to zero, in which case it's backwards-compatible with
the previous implementation in terms of identifier computation.

Update to upstream version '2.6.4'
with Debian dir 92f45f224d492f3f0b914e640c27ce17d2a9dcb7

We agreed a while ago they should be IRIs and not just URIs.

This will trigger crashes in swh.storage.cassandra, as
currently expects (wrongly) that origin urls are ASCII.

* empty fetcher name or version is not accepted by cassandra
  (and is nonsensical anyway)
* ditto for non-ASCII (and any non-printable is nonsensical)
* null bytes/chars are accepted by neither postgresql or cassandra

Update to upstream version '2.6.3'
with Debian dir 216fcda7a93684ee59ff01a0c7f8fc6021ad0e72

This is the only value we should use from now on;
and the value is ignored by swh-storage anyway.

Update to upstream version '2.6.2'
with Debian dir df6eb8e5ae3566559bfc86ac892acd3504dc130b