Fix filter functionality and performance

[ferishili]

This PR fixes #211 and covers #577,

The filter functionality problem (on page > 1) has been solved by going to first page and load resources!

The performance issue has been solved by introducing debounce mechanism on loading resources.
This also covers Filter profiles!

[github-actions]

This pull request is deployed at test.admin-interface.opencast.org/627/2024-06-05_12-57-07/ .
It might take a few minutes for it to become available.

[github-actions]

Use docker or podman to test this pull request locally.

Run test server using develop.opencast.org as backend:

podman run --rm -it -p 127.0.0.1:3000:3000 ghcr.io/opencast/opencast-admin-interface:pr-627

Specify a different backend like stable.opencast.org:

podman run --rm -it -p 127.0.0.1:3000:3000 -e PROXY_TARGET=https://stable.opencast.org ghcr.io/opencast/opencast-admin-interface:pr-627

It may take a few seconds for the interface to spin up.
It will then be available at http://127.0.0.1:3000.
For more options you can pass on to the proxy, take a look at the README.md.

[kruemelm0nsta]

in general fixed - just looks a little bit wobbly

[ferishili]

in general fixed - just looks a little bit wobbly

Right, but the problem with datepicker in the filter was not covered by the initial issue #211,
Therefore, datepicker misplacement needs to be fixed in a separate issue.

[ferishili]

#528 here is the issue regarding datepicker UI

[snoesberger]

Works mostly, but not if I'm using the start date as filter. If I go to page 3 and enter a start date filter, filtering is not working. In the browser console I do get the following error:

MUI X: A component is changing the uncontrolled value of a picker to be controlled.
Elements should not switch from uncontrolled to controlled (or vice versa).
Decide between using a controlled or uncontrolled valuefor the lifetime of the component.
The nature of the state is determined during the first render. It's considered controlled if the value is not `undefined`.
More info: https://fb.me/react-controlled-components

[ferishili]

Thanks for the testing and your feedback, I will fix it right away

[ferishili]

As an info, this error also happens in the current main branch, therefore, it would say, it is separate issue!
Here is the issue for this #636

[ferishili]

Fix for MUI error is available in #652

[lkiesow]

Probably makes sense to merge #654 first

[Arnei]

My testing confirms that this works, and the code looks good to.

[Arnei]

All other concerns seem to have been addressed (or moved), so I'll be merging this.