scheduled pools code

[DanielMorales9]

What does your PR do?

Introducing the scheduled pool implementation enables sync functionality to bump or reduce the number of pool slots on a specific recurrence.

Checklist

For all Pull Requests

• [x] Commits are signed off
• [x] Commits have semantic messages
• [x] Documentation updated
• [x] Passes ct linting

For releasing ONLY

• [ ] Chart.yaml version bumped
• [ ] CHANGELOG.md updated

[DanielMorales9]

Hi @thesuperzapper, I would like to introduce the scheduled pools to enable scheduled autoscaling policies to the sync pools. The code is very simple just like its interface as shown below:

- name: "pool"
   description: "example pool with 10 slots"
   slots: 10
   schedules:
     - name: "ScaleUp"
        slots: 28
        recurrence: 0 19 * * *
     - name: "ScaleDown"
        slots: 10
        recurrence: 0 6 * * *

[stale[bot]]

This issue has been automatically marked as stale because it has not had activity in 60 days. It will be closed in 7 days if no further activity occurs.

Thank you for your contributions.

---

Issues never become stale if any of the following is true:

1. they are added to a Project
2. they are added to a Milestone
3. they have the lifecycle/frozen label

[DanielMorales9]

Hi @thesuperzapper could you take another look at the PR? Thank you