Add pagination to orderlogs of Cycle Instructions

Current Situation
When a user expands an Order Log entry in the History view, the Web Interface displays all Task Log entries at once without pagination. This can significantly increase CPU and memory usage on the client browser, especially when thousands of Task Logs are loaded and rendered. Using a cycle instruction, thousands of task logs can be easily generated for each order.
 
Desired Behavior
Introduce pagination for Task Logs when expanding an Order Log entry, so that only a limited number of Task Logs are loaded and displayed at a time instead of loading all entries simultaneously.
 
Workaround

• Split the cycle into two separate workflows/orders (e.g., one for the morning and one for the afternoon), so the Task Logs are distributed across two Order Logs.

Maintainer Notes

• This is a feature, not a bug. The requested solution is considered for the active branch 2.9.