Currently, the following object types can be browsed from their sha1_git checksums only:
In the future, object identifiers will be computed using other hashing algorithms (sha256 for instance)
so we must prepare the webapp to handle those for browsing archived objects.
We could use the same solution as for browsing contents objects. Indeed each content has four
checksums computed for it: sha1, sha1_git, sha256 and blake2s256.
The webapp then enables to browse a content from each computed checksum using the following