Add one-off jobs for report scheduler

[jpbruinsslot]

Changes

Current situation:

• When a report schedule was created for a certain time in the future, as a manual one-off execution. It wasn't possible to reschedule that same job for a new time.
• That had to do with the scheduler checking if there was the same task already being executed in the past. And wouldn't perform a new task when it was found.

New situation:

• This pr adds support for the following Schedule scenario's:
  1. Has a cron expression, a predefined recurring schedule for when a task should be added to the queue.
  2. No cron expression, but with auto_calculate_deadline. In this case, the Scheduler type has the ability to calculate a date when the task should be added back to the queue.
  3. No cron expression and no auto_calculate_deadline. These are one-off tasks that need to be executed at a specific date.

This to make sure to enable the following functionality:

1. one-off task set at a specific date
2. recurring tasks, next date determined by a scheduler type (e.g. BoefjeScheduler calculates the next date based on prior results)
3. recurring tasks, next date determined by a cron expression

Issue link

No issue

QA notes

In combination with pr TODO: add rocky pr test if you're able to schedule a one-off report job, and reschedule it at a later date

---

Code Checklist

• All the commits in this PR are properly PGP-signed and verified.
• This PR only contains functionality relevant to the issue.
• I have written unit tests for the changes or fixes I made.
• I have checked the documentation and made changes where necessary.
• I have performed a self-review of my code and refactored it to the best of my abilities.

• Tickets have been created for newly discovered issues.
• For any non-trivial functionality, I have added integration and/or end-to-end tests.
• I have informed others of any required .env changes files if required and changed the .env-dist accordingly.
• I have included comments in the code to elaborate on what is not self-evident from the code itself, including references to issues and discussions online, or implicit behavior of an interface.

---

Checklist for code reviewers:

Copy-paste the checklist from the docs/source/templates folder into your comment.

---

Checklist for QA:

Copy-paste the checklist from the docs/source/templates folder into your comment.

[Rieven]

I've tested this branch in our upcoming branch for reuse report oois and got some errors on that deadline_at = None with validation errors for datetime object as None. The once schedules can have a deadline_at in the future. I think for reruns with once schedule should edit the schedule deadline_at to now. that would suffice. Can we not use the API endpoint to edit the schedule deadline_at?

Also we can only edit the deadline_at to now when the schedule has a deadline_at older than now

[jpbruinsslot]

I've tested this branch in our upcoming branch for reuse report oois and got some errors on that deadline_at = None with validation errors for datetime object as None. The once schedules can have a deadline_at in the future. I think for reruns with once schedule should edit the schedule deadline_at to now. that would suffice. Can we not use the API endpoint to edit the schedule deadline_at?

Also we can only edit the deadline_at to now when the schedule has a deadline_at older than now

I personal correspondence I mentioned that the model definition in rocky for a Schedule had to change to support the None value for a deadline_at

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud