It also enables to remove the version restriction on psycopg2.

Related to swh/infra/sysadm-environment#4772

1. Follows the AtomPub <https://datatracker.ietf.org/doc/html/rfc5023\#section-5.2\>
   spec
2. Discoverable from the service document
3. Makes more sense semantically to have the list of items in a path
   at the root of that path.

This adds a paginated listing endpoint so authenticated user can retrieve their deposit
information in batch. This touches another part of an equivalent private listing api to
allow paginated code reuse.

That new endpoint is not a sword endpoint but it lists deposits in xml relatively sword
like nonetheless.

Related to T2996

SWORD doesn't require them to be the same, and IMO it is clearer
if we keep them separate.

Related to T2610

Dropping the redundant SWH or Deposit terms along the way.

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

Related to T2140

Related T857

This possibly aggregates multiple archives into one and stream the
result to the client.

This is incomplete for now as the possibly temporary archive
referenced is left on the server.

A client can access collections.

Beware:

- Update means replace existing metadata/archive with new ones.
In effect, this replaces the previous deposit information.

- Add: add new metadata/archive to existing deposit

To:
- update existing metadata to an existing deposit
- add new metadata/archive to existing deposit
- display the actual deposit's metadata

Be uniform with the service document endpoint.
Be consistent with the service document endpoint response.

And add status endpoint