browse pages should not ignore sort config from back end

[jensvannerum]

References

• Fixes Browse pages don't take into account sort configuration DSpace#8651
• 7.x branch for backport: https://github.com/atmire/dspace-angular/tree/w2p-122064_browse-pages-ignore-sort-config-fix-UI

Description

Introduces a new service method to obtain the configured sort direction of a browse index which is then used in the relevant browse components to do the initial fetch. Manually changing sort direction on page will override the configuration of course.

Instructions for Reviewers

In your dspace.cfg change some of the default browse indexes by adding a custom sort order to them ("adding :desc at the end as they currently default to asc)

• Verify the browse index loads with this sort order applied
• Verify manually changing pagination / sort order still works as intended
• Verify all other browse functionality still works as intended

Checklist

This checklist provides a reminder of what we are going to look for when reviewing your PR. You do not need to complete this checklist prior creating your PR (draft PRs are always welcome).
However, reviewers may request that you complete any actions in this list if you have not done so. If you are unsure about an item in the checklist, don't hesitate to ask. We're here to help!

• My PR is created against the main branch of code (unless it is a backport or is fixing an issue specific to an older branch).
• 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 npm run lint
• My PR doesn't introduce circular dependencies (verified via npm run 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.
• My PR aligns with Accessibility guidelines if it makes changes to the user interface.
• My PR uses i18n (internationalization) keys instead of hardcoded English text, to allow for translations.
• My PR includes details on how to test it. I've provided clear instructions to reviewers on how to successfully test this fix or feature.
• 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.

[github-actions]

Hi @jensvannerum,
Conflicts have been detected against the base branch.
Please resolve these conflicts as soon as you can. Thanks!