Fixed community's sub-communities and collections sort

[alexandrevryghem]

References

• Fixes DESC sort not working in list of sub-communities/sub-collections #2160
• Requires Fixed community's sub-communities and collections sort DSpace#8841

Description

Fixed community's sub-communities and collections sort options from url being ignored when making the request to the backend (meaning that after refreshing the page your sort options would be lost). The pagination options for sub-communities were also lost after refreshing the page.

Instructions for Reviewers

List of changes in this PR:

• Made changes to the CommunityPageSubCollectionListComponent & CommunityPageSubCommunityListComponent to retrieve the pagination options and the sort options from the url when available.

Guidance for how to test this PR:

• After testing the backend PR you should have a community containing at least 2 sub-communities and 2 collections with different names and go to the parent community page
• Click on the gear next to the collections and to the sub-communities and select Descending
• Check that the collections and the sub-communities are sorted in descending order
• Check that after refreshing the page the collections and the sub-communities are still sorted in descending order
• Click on the gear next to the collections and to the sub-communities and select Ascending
• Check that the collections and the sub-communities are sorted in ascending order
• Check that after refreshing the page the collections and the sub-communities are still sorted in ascending order
• Set the page size for the sub-communities to 1
• Check that after refreshing the page the page size is still 1

Checklist

• My PR is small in size (e.g. less than 1,000 lines of code, not including comments & specs/tests), or I have provided reasons as to why that's not possible.
• My PR passes ESLint validation using yarn lint
• My PR doesn't introduce circular dependencies (verified via yarn check-circ-deps)
• My PR includes TypeDoc comments for all new (or modified) public methods and classes. It also includes TypeDoc for large or complex private methods.
• My PR passes all specs/tests and includes new/updated specs or tests based on the Code Testing Guide.
• If my PR includes new libraries/dependencies (in package.json), I've made sure their licenses align with the DSpace BSD License based on the Licensing of Contributions documentation.
• If my PR includes new features or configurations, I've provided basic technical documentation in the PR itself.
• If my PR fixes an issue ticket, I've linked them together.

[tdonohue]

👍 Thanks @alexandrevryghem ! As noted in the backend PR review, tested this today and everything is working. Code looks good too.