Update to upstream version '0.0.66'
with Debian dir 5dc3c4da5fb7b38713071c51e0eb2e0ccc3189e9

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

Update to upstream version '0.0.65'
with Debian dir 186667db6d343fd83910bbd0aec7ddb83f5e6b75

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

Update to upstream version '0.0.64'
with Debian dir 8a7feb21ef6754ee9319b12458178e009794d67e

Hinting at the origin_visit_update model

Related to T2310

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.

Fix keyword parameters transmission to snapshots_d strategy.

Ensure max_size constraint is respected when fixing snapshot aliases.

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

instead of a reference to an Origin entity.

for each entity model `Model`, provide a `models_d` strategy that
produces dicts suitable for using as argument for the `Model.from_dict`
factory method, and reimplement the `models` generator using this
former hypothesis generator.

This is needed to help writing low level tests for model entities.

- 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.

Update to upstream version '0.0.63'
with Debian dir 279c24fac8517e2a8272d9494793afe688b4d950

(pairing with @vlorentz)

Related to T2310

Update to upstream version '0.0.62'
with Debian dir b55f8a89978085d75b15a56406a3b3edd1fc2dc9

These are expected to be bytes, not str.

this does not work in the general case since there is no (recursive)
convertion of objects used as model object initialization.

We can only check when using the from_dict() factory.

for better clarity on the code author's intention.

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