Removed observable function calls from template (part 1)

[alexandrevryghem]

References

• Fixes Opening the simple item page of a withdrawn item when logged in as administrator stalls the frontend instance #3393
• Fixes Browser hangs due to infinite loop when editing groups #3257
• Fixes Lack of community/collection information when editing a person's access control #3571

Description

Currently, there are multiple instances where observable function calls are subscribed to directly in the template. This is considered a bad practice, as it cause a new Observable to be recreated each time Angular’s change detection is triggered. Some instances of this issue remain, but I will work on creating PRs to address them over the coming months.

Instructions for Reviewers

Guidance for how to test & review this PR:

• Verify that the 3 linked issues have been resolved
• Verify that all these functionalities still work correctly:
  • EPerson pages
  • Group pages
  • Bitstream Format Registry
  • Metadata Registry
  • A component that uses the pagination component

Checklist

• 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.