Currently JobOperator supports getting job executions by job instance (getting all job executions belonging to that job instance), or getting running job executions by job name.

Users should be able to get all job executions belonging to a job name.

With the current JobOperator, the workaround is, first to first get all job instances for a job name, then for each job instance, get all job execution belonging to that job instance. This is not efficient, especially with jdbc job repository.

Job repository and all its subtypes will all need to support this additional operation.