Fix 6076: Item page search components reload entire page

[abelc-escire]

References

• Fixes Item page search components reload entire page #6076

Description

Apply changes to avoid a reload screen when filters, query, search bar, and other URL parameter changes occur, and move to the top of the search component.

Instructions for Reviewers

To test it, we need to move to a search screen (collections, items, communities), and now in the results we can select a Filter in the lef side, move to the bottom and select a pagination or even search y the search input bar and now the behavior shouldn't reload the screen instead of that we should be able to reload all the data without refresh the whole screen and the scroll position should be on the top of the search bar.

List of changes in this PR:

• Avoid reloading the screen when we apply a filter/query parameter.
• Move the scroll to the top of the search component instead of the top of the page when we refresh the search properties on the URL parameters.

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 follows all coding best practices based on the Code Conventions Guide
• 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.