feat: Support a dynamic minimum interval for alerts and reports

[Vitor-Avila]

SUMMARY

This PR adds the ability to control the ALERT_MINIMUM_INTERVAL and/or REPORT_MINIMUM_INTERVAL configs dynamically (rather than having it statically defined during runtime). This is useful in case the value should be dynamically changed/evaluated on demand (you might want to control it externally).

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

No UI changes.

TESTING INSTRUCTIONS

Added unit tests to make sure the config supports both an integer and a callable.

ADDITIONAL INFORMATION

• Has associated issue:
• Required feature flags:
• Changes UI
• Includes DB Migration (follow approval process in SIP-59)
  • Migration is atomic, supports rollback & is backwards-compatible
  • Confirm DB migration upgrade and downgrade tested
  • Runtime estimates and downtime expectations provided
• Introduces new feature or API
• Removes existing feature or API

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 83.73%. Comparing base (76d897e) to head (1e8635c).
Report is 1094 commits behind head on master.

Additional details and impacted files

@@             Coverage Diff             @@
##           master   #29241       +/-   ##
===========================================
+ Coverage   60.48%   83.73%   +23.24%     
===========================================
  Files        1931      518     -1413     
  Lines       76236    37541    -38695     
  Branches     8568        0     -8568     
===========================================
- Hits        46114    31435    -14679     
+ Misses      28017     6106    -21911     
+ Partials     2105        0     -2105     

Flag	Coverage Δ
hive	48.94% <0.00%> (-0.23%)	⬇️
javascript	?
mysql	77.21% <50.00%> (?)
postgres	77.34% <50.00%> (?)
presto	53.56% <0.00%> (-0.25%)	⬇️
python	83.73% <100.00%> (+20.24%)	⬆️
sqlite	76.80% <50.00%> (?)
unit	59.24% <100.00%> (+1.61%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[betodealmeida]

Nice!

One comment I had, I wonder if we should have some parameters passed to the function, even if your examples don't need them. This way we don't need to change the signature in the future. Eg, we could pass the database, so that databases where query are more expensive would have a higher minimum interval.

[Vitor-Avila]

@betodealmeida that makes perfect sense! I added **kwargs to the example method so that if in the future additional work is done to pass parameters, this shouldn't break any existing setup.