Avoid ordering in data tables with new Ajax requests

[mschnitzer]

Is your feature request related to a problem? Please describe.
The maintenance overview page has now been refactored and I just tested the new ordering feature for the datatables. However, when I clicked the arrow down/arrow up to order by the summary, nothing happened. After a while I was just scrolling around on that page to see what else has been changed and then the whole data table was refreshed. I was a bit confused and then I realized that the ordering (which seemed to not work before) just fetched the whole data records via Ajax again and after its completion (which took 18,2 seconds) it was replaced with the old table.

This is really confusing because you expect the ordering to happen within milliseconds and being done by your browser instead of querying information from the database again.

Describe the solution you'd like
Order in the browser, not via an Ajax call.

Describe alternatives you've considered
n/a

Additional context
n/a

[bgeuken]

Order in the browser, not via an Ajax call.

This would only be possible without using server side pagination.

Seems we would have to make this page / querying incidents much faster before the ordering option is of any user. Until then we should disable it.

[vpereira]

Either you load everything and then allow the user to paginate it locally in the browser or you use pagination, getting the initial results fast but then hitting the server again if you need to resort it.. I think that's an expected dichotomy

[mschnitzer]

Maybe this one is not needed when #7507 is implemented. This would at least solve the issue on the maintenance page. Not sure if it's a problem for other pages as well.