Removed unused ListableModule

[alexandrevryghem]

References

• Related to Restore dynamic component decorators #4528

Description

In #4528 the dynamic decorator logic was restored. That PR removed all the usages of the ListableModule, but it looks like that file got accidentally restored (propably caused by the merge of #4446). This PR simply removes this module again & the lazy-listable-components.ts files.

When this is merged we will also have to update the migration docs to remove the "lazy-listable" references

Instructions for Reviewers

List of changes in this PR:

• Deleted the ListableModule & all the lazy-listable-components.ts files in the themes

Guidance for how to test and review this PR:

• Since this is unused code this shouldn't break anything but you can test that the listable objects like the item pages & the search results still work

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