Problem: Job redo Option

[maennchen]

This is a follow up for #240

Jobs should have the option to configure how to handle a downtime of the scheduler.

1. transient jobs that do not need redo-ing even if their execution was skipped
2. permanent jobs that would like to get executed once after the period of scheduler being down (no matter how many cycles they have missed). Like backup jobs.
3. permanent_consecutive - (a better name is more than appreciated) that need to be redone exact the number of times they were not executed. I can imagine like jobs incrementing some counters. I believe I would be able to come up with a real-world scenario, but I need some thinking to come up with it.

[jonathanhickford]

Any mileage in an option that gives the permanent_consecutive scheduled jobs the information to determine itself what to do?

For example say I have a job scheduled every hour which has the purpose of sending reminder notifcations. If I missed a number of runs I might want to only send reminders for events that have not yet happened.

I think for that usecase I'd want to be able to pass the job arguments for both:

1. The time the scheduler would have run the job at
2. The time the scheduler is running the job at

[maennchen]

@jonathanhickford I'll consider that when implementing it. I'm already working on v3 where this should be included. Since I'm doing that in my free time it'll take some time though.