[OPTIM] Update JobExecution entity regardless of the batch size

This optimisation aims at strengthening the job execution itself.

The current implementation fails if x products take more than y seconds to be processed before they are effectively written. x is the batch size, y is usually the wait_timeout set on the database server side.

It can fail because the job statistics are updated by a separate SQL connexion which can idle for the whole batch size.

The optimisation consists in updating the JobExecution entity every 10 seconds, only if it's not updated when the item count is a multiple of the batch size.

| Q                    | A
| -------------------- | ---
| Bug fix?             | not really
| New feature?         | not really
| BC breaks?           | no since the default code is not altered ([if untouched oldcode] / [elseif with newcode])
| CI currently passes? | 
| Tests pass?          | 
| Scenarios pass?      | 
| Checkstyle issues?*  |
| PMD issues?**        |
| Changelog updated?   | yes
| Fixed tickets        |
| DB schema updated?   | no
| Migration script?    | no
| Doc PR               | no