The job progress reporter should allow progress reports more often

[Nicklas Nordborg]

The current job progress reporter ignore updates unless at least 5 seconds has passed since the last update or the progress has increased by at least 5%.

I think it is a bit too restrictive. The typical use case is that in a multi-step procedure that last progress report in one step may come too close to the next progress report in the following step (which is ignored). Since the first progress report in step is often too execute a big query it seems like the job is stuck at the previous step.

One idea to improve this is to cache the current progress and then use a timer that at regular intervals makes the actual update.

[Nicklas Nordborg]

(In [7157]) Fixes #2010: The job progress reporter should allow progress reports more often

The original idea with a timer seemed a bit too complex to implement. It would have been easy enough to start the timer, but there is no immediate hook to stop it.

Instead, the limitations has been relaxed a bit so that only 1% difference or 2 seconds is needed for an update to occur.