Changes to schedule all reports, even for once

[Rieven]

Changes

• A report creation will be now executed through the scheduler.
• All reports are scheduled, you can schedule a report once (for now) or on a specific date
• Report Recipe will be always present voor every report
• Schedule once will have a cron of None, making it possible to schedule it only on the deadline_at (start date and time)
• This feature will work after Support a Schedule without a schedule in scheduler #3834 is merged because it make it then possible to schedule once.
• Report names will only consists of formatted name as even for once, it will replace ${report_type} {ooi} {oois_count} depend on the formatted name.
• Renaming of individual reports can be done after merging: Add bulk actions on report overview #3777
• The datetime widget is going to be seperated and implemented after merging: Add start time to scheduled reports #3809
• We need to also merge: Add auto_calculate_deadline attribute to Scheduler #3869 to not reschedule task when choosing once.

Issue link

#3753

Closes #3753

Demo

QA notes

You will need to restart the report runner.

---

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.

[ammar92]

Nice work, looks good to me 👍 The PR is quite detailed, thanks for that. Just a small note for the next time: please remove the boilerplate text (in the "Issue link" section, either fill it in or remove the section entirely)

[ammar92]

There's still an issue with the tests. Apparently a ReportRecipe.cron_expression doesn't like None objects

[Rieven]

There's still an issue with the tests. Apparently a ReportRecipe.cron_expression doesn't like None objects

Yes, this will be fixed probably when the Pr of JP is merged with main, also the test fix :)

[RomijnHumanoids]

As mentioned in the meeting just now, this suggestion actually matches previous design of selecting the start date for reports 👍. I've provided a screenshot in this comment.

[Rieven]

As mentioned in the meeting just now, this suggestion actually matches previous design of selecting the start date for reports 👍. I've provided a screenshot in this comment.

We continue with implementation of time widget as per:
#3809