activity background works should'nt list unpredictable results length

When displaying the background works page, we cannot predict how much entries will be displayed in scheduled and completed table. This may break the server memory. We should either display only the counters and the running works (which will limited to the number of worker threads allocated in the cluster).