♻️ REFACTOR: Move archive backend to aiida/storage

[chrisjsewell]

This PR moves the archive storage backend implementation (sqlite_zip) into aiida/storage
alongside the "main" psql_dos backend.
It includes both the storage reading and migration functionality.

Inline with this synchronisation of the archive and the storage backend:

• A number of the archive specific exceptions have been replaced with general storage ones:
  • UnreadableArchiveError/CorruptArchive -> CorruptStorage
  • IncompatibleArchiveVersionError -> IncompatibleStorageSchema
  • ArchiveMigrationError -> StorageMigrationError
  • ArchiveClosedError -> ClosedStorage
• MIGRATE_LOGGER has been moved to aiida/storage/log.py
• verdi archive inspect has been deprecated
  and replaced by verdi archive version and verdi archive info,
  to bring it inline with verdi storage.

alembic migrations have been added to the sqlite_zip migration logic,
to support future migrations of the sqlite database.
Alongside this, the non-null restrictions for legacy archive fields have been relaxed,
to improve robustness.
Subsequent migrations have been added;
first, to replace any existing (unwanted) null values with default values,
then to modify the schema to re-add the non-null constraints.

Finally, additional tests have been put in place (in tests/tools/archive/test_schema.py),
to ensure that the sqlite schema is always synchronised with the postgresql schema.

---

Notes

Writing of archive files is still specific to the archive functionality, due to the design constraint of an archive being contained within a single file.
Because of this, one cannot efficiently modify an existing archive, without

This should also eventually allow for the aiida/tools/archive/create.py::create_archive and aiida/tools/archive/imports.py::import_archive functions to be "re-conceptualised" as simply transfers of data between storage backends (see also aiidateam/AEP#31)

[chrisjsewell]

Ok this is just about done, so ready for review.
I'll update the initial PR comment with some more description later

some potential TODOS:

• Address Improve message when dangling nodes or links are found in verdi archive import #5378 and Improve messages of verdi archive import for old archives #5377
• Currently, non-nullable constraints are applied directly on the conversion from JSON to SQLite.
  But perhas there may be some old archives that are not compatible with these constraints,
  so instead we should first allow null fields, then apply non-nullability retroactively (like aiida/storage/psql_dos/migrations/versions/1de112340b17_django_parity_2.py)
• Address Testing (and documenting, and possibly improving) what happens with concurrent archive imports #5389

[sphuber]

Thanks @chrisjsewell . I have given it a bit of a look, but there is too much to really do it in detail and since this needs to go in for the beta release, I am approving. We should test ourselves the new archive functionality soon such that any bugs can be fixed a.s.a.p.

[chrisjsewell]

We should test ourselves the new archive functionality soon such that any bugs can be fixed a.s.a.p.

Way ahead of you 😉 I already added #5407 on Friday

Just gotta update the PR description, then I'll merge