feat: migrate to standalone components, directives, pipes

[enea4science]

Is your feature request related to a problem? Please describe.
No. But having big SharedModule is an anti-pattern and slows down compilation times.

Describe the solution you'd like
Having standalone components, directives and pipes makes it easier to think about the dependencies of the components and are easier to refactor.

The official standalone migration schematic does 99% of the work:

ng generate @angular/core:standalone

There are some places where we need to use the forwardRef for components that are used before initialisation, but those were easy fixable.

I did a test, and the migration worked fine, the project compiles fine and didn't have any thing broken from a quick look I had.

Not all tests pass (even though they get updated by the schematic), but most of them fail because of providers, and those are easily fixable imo.

Additional context
Here are screenshots from what I tried:

[enea4science]

Also, there would be no need for LazyThemeModule as standalone fixes the context issue.

[tdonohue]

@enea4science : Thanks for this... I like this idea overall, but I suspect it needs discussion from others. I've linked this ticket into our Developers Meeting agenda for this week, as it sounds semi-related the the Angular refactor proposal that @atarix83 will talk about. This ticket seems to me to suggest a first step towards cleaning up our existing Angular components. https://wiki.lyrasis.org/display/DSPACE/2023-07-20+DSpace+Developers+Meeting#id-20230720DSpaceDevelopersMeeting-Agenda