Fix cron for last day of the month

[madelondohmen]

Note: This PR is based on PR #3809

Changes

Small fix when the start day is the 28th, 29th, 30th or 31st of the month. Will be processed as the last day of the month ("L").

Issue link

Closes #3810

Demo

Please add some proof in the form of screenshots or screen recordings to show (off) new functionality, if there are interesting new features for end-users.

QA notes

• Create a scheduled report
• Select a date on the 28th (or 29th, 30th or 31st)
• Select recurrence "Monthly"
• Check if the cron is something like h m L * * where h is the hour, m the minute and L should be "L"

---

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]

A tip for the next time: It's a bit hard to review this since there's duplicate code due to merging of feature/add-start-time-to-schedule.

I think it would've been better to branch from feature/add-start-time-to-schedule instead and make the PR merge from feature/cron-last-day-of-month to feature/add-start-time-to-schedule

[stephanie0x00]

Checklist for QA:

• I have checked out this branch, and successfully ran a fresh make reset.
• I confirmed that there are no unintended functional regressions in this branch:
  • I have managed to pass the onboarding flow
  • Objects and Findings are created properly
  • Tasks are created and completed properly
• I confirmed that the PR's advertised feature or hotfix works as intended.
• I checked the logs for errors and/or warnings and made issues where necessary

What works:

Seems to work.

What doesn't work:

n/a

Bug or feature?:

n/a

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarQube Cloud