Account for workloads exceeding cycle period

**Motivation**
it's possible for some workloads (accounts with many resources) to exceed the time we allow for cycles to run. this would result in cloudbeat always reporting partial findings, as each cycle would end before scanning is complete. (see https://github.com/elastic/cloudbeat/pull/2055#discussion_r1567816827 and https://github.com/elastic/cloudbeat/pull/2055#discussion_r1568318377)

**Definition of done**
- [ ] come up with a mechanism to allow cloudbeat to resume a cycle if the previous one didn't finish, while avoiding infinite cycles

**Related tasks/epics**
- https://github.com/elastic/cloudbeat/issues/2054