Add next_run attribute to job create
Add functional tests for job next run integrity checks
Allow job scheduler to handle duplicate job creation
Scheduler to pass in next run for integrity checks
Add atomic operation for setting next run in db layer
have job creation in the api verify the expected next_run
Only grab one page at a time in scheduler

There is not a need to grab all of the available schedules in every iteration of
the job scheduler. This can lead to very big lists that must be iterated, instead
the scheduler will just continue with the remaining jobs in it's next iteration.
Merge pull request #127 from ameade/rm-sched-pagi

Only grab one page at a time in scheduler
Fix coverage settings
Pick a new random port if one is in use in functional tests
Tweaking default worker log filename to match other services.
Merge pull request #130 from esheffield/master

Change default worker log filename
Merge pull request #129 from ameade/fragile

Pick a new random port if one is in use in functional tests
Merge pull request #128 from ameade/fix-cover

Fix coverage settings
Merge pull request #126 from ameade/job-integrity

Verify schedule hasn't changed when creating a job