Add a new method to the JobRepository interface (perhaps a variant of getJobExecutionsByJob(jobName)), which would make it possible to fetch only subset of job execution records for given job.

Rationale for this change is to provide a way for an application container admin to optimize deployment times in cases when job repository contains large number of job execution records (say hundreds thousands or more). Application deployment times in Wildfly are affected in such sutations because the app container loads all existing job execution records during the app deployment, which can take significant amount of time. Enabling app containers to request only subset of job execution records provides a way to overcome this issue.