This is a step forward having model objects, declared as frozen, immutable.

This requires attrs_strict >= 0.0.7.

this attribute is not an intrinsic property of a content object, so it
should not be used when comparing or hashing.

Simply add a BaseModel.anonymize() method. Default implementation returns
None, meaning the object is not anonymizable.

For Person, the method returns a Person whith hashed fullname (and unset
name and email).

For Revision and Release, the method returns an anonymized version of
the object, i.e. with instance of Person replaced by anonymized ones.

This also adapts the hypothesis strategies, using the plural form
origin_visit_statuses. That plural form is acceptable because in our context,
the statuses are countable.

Related to T2310

- blackify all the python files,
- enable black in pre-commit,
- add a black tox environment.

A release may have an empty message, for instance those derived from
a Mercurial repository.

So make that field optional to avoid type validation errors.

With support for str representation of date.
Mostly for testing purpose.

instead of a reference to an Origin entity.

- add a validator for negative_utc (can be True iff offset is 0),
- update the timestamps_with_timezone hypothesis strategy,
- add low-level tests for it.

This ensures all instanciated model entities have valid types for attributes.

Related to T2308.

(pairing with @vlorentz)

Related to T2310

it was still here for bw-compat but should not be necessary any more.

this function does not need to be a local function of the to_dict namespace.

This will allow deduplicating code across loaders.

This lets us generate Content objects directly from a bytestring, with the
proper set of hashes auto-generated from the contents.

Required by loaders, when they can't parse the fullname.

Will be used by loaders.

They will be used by loaders, so they can deal only with
model objects, instead of having to do the same conversion themselves.

This removes the `data` and `save_path` arguments of `from_file` and
`from_disk`, as data loading is always deferred from now on.
To access it, users are now expected to either open the data files
themselves, or us `.to_model().with_data()`.

Can be useful to deduplicate code in swh-storage.

It already is in practice.

The current postgresql model refuses NULL values.

Related to P589

Related to T2188

Add support to automatically compute identifier in the following object models:
Directory, Release, Revision, Snapshot.

If the identifier is not provided as parameter, it will be computed when the model
is initialized.

we do not really need them to be mutable, plus we gain their instances now
being hashable, so we can add them in set() for example.

Instead of relying on attr.asdict recursion, we do recursion ourselves. This
simplifies a lot of the inherited to_dict() methods.

Needed by the replayer in swh-journal.

It kind of matches the current state of the postgresql storage, which
does not support it.