ENH: apply paging such that no unwanted jobs are being triggered

Summary

Performance was bad because a paged retrieve would also load and execute jobs for entities which are not on the requested page.

Focus

Two things happened:

1. There was a trivial but wrong implementation of Entity#skipJob(). Jobs would never be skipped, even if an entity had entity status IGNORE. This was a one-liner.
2. Because the paging was being applied after the query (and other jobs) some (and possibly A LOT) entity jobs would be added to the schedule which are not necessary because the entities are not the requested page. This is the rest of the changes.

Test Environment

Unit test should be sufficient.

Check List for the Author

Please, prepare your MR for a review. Be sure to write a summary and a focus and create gitlab comments for the reviewer. They should guide the reviewer through the changes, explain your changes and also point out open questions. For further good practices have a look at our review guidelines

• All automated tests pass
• Reference related issues
• Up-to-date CHANGELOG.md (or not necessary)
• Annotations in code (Gitlab comments)
  • Intent of new code
  • Problems with old code
  • Why this implementation?

Check List for the Reviewer

• I understand the intent of this MR
• All automated tests pass
• Up-to-date CHANGELOG.md (or not necessary)
• The test environment setup works and the intended behavior is reproducible in the test environment
• In-code documentation and comments are up-to-date.
• Check: Are there specifications? Are they satisfied?

For further good practices have a look at our review guidelines.