Make the number of communities on the home page configurable

[alawvt]

Is your feature request related to a problem? Please describe. In DSpace 7, there are only 5 top-level communities listed on the home page, https://demo7.dspace.org/home. When the user clicks on the next page they see the next 5 communities. This is too slow.

In DSpace 6 XMLUI, all the top-level communities are listed on the home page, https://demo.dspace.org/xmlui/, which helps the user immediately find the right one. Administrators, too, want to see the entire list without multiple clicks.

Describe the solution you'd like One solution would be to make the number of communities per page configurable with a number, or perhaps, an option, "all." Since the time to load the home page in DSpace 6 XMLUI is acceptable, I don't think a large number or "all" would be a problem and would certainly be less time than waiting for multiple pages.

Describe alternatives or workarounds you've considered A clear and concise description of any alternative solutions or features you've considered.

Additional context Add any other context or screenshots about the feature request here.

[tdonohue]

Agreed, this should be configurable. It appears to be hardcoded here: https://github.com/DSpace/dspace-angular/blob/main/src/app/home-page/top-level-community-list/top-level-community-list.component.ts#L57

This likely could be fixed in a similar manner to @mwoodiupui 's #1771. It just needs a configuration to be added and used in that top-level-community-list.component.ts.

Pulling this over to our 7.4 board in the hopes of a volunteer. It seems like something that might be fixed very quickly. (@mwoodiupui , let me know if you are interested in this one as well, or just assign it to yourself if you want it)

UPDATE: Note to future developers. This might be done at the same time as #1750, perhaps even using the same config. See this comment https://github.com/DSpace/dspace-angular/issues/1750#issuecomment-1224711236

[mark-cooper]

@tdonohue I've had a request for this and it seems straightforward enough that I'm happy to volunteer for it (and #1750).

[tdonohue]

@mark-cooper : Sounds great! Please feel free to submit a PR when you are completed, and link the PR back to both tickets (Using "Fixes" or "Resolves" keywords from Github)