fix(cron): schedule accepts supported formats

[wass3r]

❤ THANKS FOR HELPING OUT :D

Proposed change

Addresses a regression that prevents the usage of all the supported scheduling formats, such as passing timezone into the schedule (eg. CRON_TZ=Asia/Tokyo 30 04 * * *) or predefined schedules (eg. @every 5m).

fixes #145

Types of changes

What types of changes is this pull request introducing to flottbot? Put an x in the boxes that apply

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist

You can fill this out after creating your PR. Put an x in the boxes that apply

• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation (if appropriate)

[coveralls]

Pull Request Test Coverage Report for Build 203a1a474c89d16bb43138f6094e5e11c5c3ad5f-PR-149

• 0 of 20 (0.0%) changed or added relevant lines in 1 file are covered.
• 1 unchanged line in 1 file lost coverage.
• Overall coverage decreased (-0.2%) to 36.514%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
remote/scheduler/remote.go	0	20	0.0%

Files with Coverage Reduction	New Missed Lines	%
remote/scheduler/remote.go	1	0%

Totals
Change from base Build 048d1f21648a77956141462365b468c5eebec34b:	-0.2%
Covered Lines:	838
Relevant Lines:	2295

---

💛 - Coveralls

[wass3r]

just calling out this part (SkipIfStillRunning) as it may be too opinionated. it seemed like a decent, sensible default, but i can be convinced to take it out or control it via flag as there might be use-cases 🤷‍♂️

ref: https://pkg.go.dev/github.com/robfig/cron/v3@v3.0.1#SkipIfStillRunning