CHAOSPLT-531: Add a config for the minimum cron frequency

[ptnapoleon]

What does this PR do?

• Adds new functionality
• Alters existing functionality
• Fixes a bug
• Improves documentation or testing

Please briefly describe your changes as well as the motivation behind them:

• One might consider a disruption that runs every minute to be too often. One might even want to prevent that. Now we can!

Code Quality Checklist

• The documentation is up to date.
• My code is sufficiently commented and passes continuous integration checks.
• I have signed my commit (see Contributing Docs).

Testing

• I leveraged continuous integration testing
  • by depending on existing unit tests or end-to-end tests.
  • by adding new unit tests or end-to-end tests.
• I manually tested the following steps:
  • x
  • locally.
  • as a canary deployment to a cluster.

[datadog-datadog-prod-us1]

Datadog Report

Branch report: philip/chaosplt-531
Commit report: ecfa535
Test service: chaos-controller

✅ 0 Failed, 979 Passed, 8 Skipped, 25m 44.18s Total Time
❄️ 1 New Flaky

New Flaky Tests (1)

• [It] Disruption Controller dont duplicate targets across disruptions should target all the selected pods - Controller Suite - Last Failure

  Expand for error

   A grace period timeout occurred
   
   [TIMEDOUT] A grace period timeout occurred
   In [DeferCleanup (Each)] at: /home/circleci/go/src/github.com/DataDog/chaos-controller/controllers/suite_toolsfor_test.go:217 @ 12/04/24 16:48:55.888
   
   This is the Progress Report generated when the grace period timeout occurred:
     Disruption Controller dont duplicate targets across disruptions should target all the selected pods (Spec Runtime: 16m56.011s)
       /home/circleci/go/src/github.com/DataDog/chaos-controller/controllers/disruption_controller_test.go:255
       In [DeferCleanup (Each)] (Node Runtime: 30.001s)
         /home/circleci/go/src/github.com/DataDog/chaos-controller/controllers/suite_toolsfor_test.go:217
   ...