Fix issue where scoped browse by would not inititialze correct component

[jensvannerum]

References

• Fixes Error browsing by title, date, or subject category in a community/collection #3840
• Related to Get rid of unnecessary and failing REST requests when navigating between different browse indexes  #3753 as this applies the same fix, but to scoped browse-bys

Description

Makes sure the browse-by-switcher component picks up changes in browse type, so the component gets rendered correctly

Instructions for Reviewers

Please add a more detailed description of the changes made by your PR. At a minimum, providing a bulleted list of changes in your PR is helpful to reviewers.

Test that switching between all types of browses works, both for scoped and non scoped browse pages

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.

[toniprieto]

Thanks @jensvannerum ! Just tested it, everything works fine now!

[tdonohue]

👍 Thanks @jensvannerum ! Merging based on test by @toniprieto (thanks as well!). Code looks good to me

[dspace-bot]

Backport failed for dspace-7_x, because it was unable to cherry-pick the commit(s).

Please cherry-pick the changes locally and resolve any conflicts.

git fetch origin dspace-7_x
git worktree add -d .worktree/backport-3845-to-dspace-7_x origin/dspace-7_x
cd .worktree/backport-3845-to-dspace-7_x
git switch --create backport-3845-to-dspace-7_x
git cherry-pick -x 32fae27c7a34297e16cab7f01c37064bd9ed1ba0

[dspace-bot]

Successfully created backport PR for dspace-8_x:

• [Port dspace-8_x] Fix issue where scoped browse by would not inititialze correct component #3848

[tdonohue]

@jensvannerum : This appears to have failed backport to dspace-7_x because the code is much different in that release. I'm attempting to determine however if this fix is even necessary in 7.x. Could you verify whether this fix is needed in 7.x, and, if so, create a backport?