Optimize calls to the volatile API for display of current result list

Current Situation

• Calls to the JOC Cockpit REST Web Service volatile API are performed for the selected folder and status of all entries that are returned in the Jobs View, Job Chains View and Orders View. This causes performance penalties for large result sets.
• Example: If a a list shows 10 entries per page and the list contains 200 items then 200 calls to the volatile API are performed at the time of rendering the list. This will cause delays to display results.
• This behaviour allows a user to 'search in results', to perform sorting, to change the number of entries per page and to switch pages quickly.

Desired Behavior

• Calls to the permanent API are performed with user selected parameters for all entries. Then calls to the volatile API are performed exclusively for entries that become visible to the user.
• Calls to the volatile API are performed every time when a user changes the number of entries per page, switches to a page number or performs sorting. Such calls are performed only once per object, e.g. the information is re-used if a user switches back to a page of a result list.
• The operation 'search in results' is performed for attributes that are returned by the permanent API only.