Restoration of Dspace Communities/sub-communities/collections hierarchy

[caflynn]

The basic hierarchical structure of every DSpace site, regardless of the version, is to have communities and sub-communities, which contain collections, which contain items. (Communities cannot store items directly. In order to store an item, a community must contain at least one collection, which can then hold the item.)

The public display needs to directly reflect this long-established hierarchy of Communities/sub-communities/collections/items. In order to precisely see the way the holdings should be represented in Scholars' Bank, we would need to be able to look at our pre-migration server. For example, the way Communities and and Collections in this Community are displaying one after the other as they are on the following page, rather than branching with the hierarchy, violates the normal Communities/sub-communities/collections hierarchy of DSpace-- which is version agnostic.

This tickDescribe the bug
A clear and concise description of what the bug is. Include the version(s) of DSpace where you've seen this problem. Link to examples if they are public.

To Reproduce
Steps to reproduce the behavior:

1. Do this
2. Then this...

Expected behavior
A clear and concise description of what you expected to happen.

Related work
Link to any related tickets or PRs here.