feat(crons): Backfill new broken monitor setting

[davidenwang]

Backfills the new broken monitor setting according to the previous value we were using which was from "Nudges" (approval)

[github-actions]

This PR has a migration; here is the generated SQL for src/sentry/migrations/0742_backfill_broken_monitor_notification_setting_option.py ()

--
-- Raw Python operation
--
-- THIS OPERATION CANNOT BE WRITTEN AS SQL

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 78.12%. Comparing base (fe84550) to head (80e475d).
Report is 48 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master   #74415   +/-   ##
=======================================
  Coverage   78.11%   78.12%           
=======================================
  Files        6676     6676           
  Lines      298721   298729    +8     
  Branches    51424    51427    +3     
=======================================
+ Hits       233338   233374   +36     
+ Misses      59095    59062   -33     
- Partials     6288     6293    +5     

see 26 files with indirect coverage changes

[markstory]

Do we need to remove the approval type setting?

[davidenwang]

nah, the approval setting still exists and will control other classes of notifications, just wanted to split out broken monitor emails into its own category with this migration

[markstory]

If there is an existing row for brokenMonitors does the value need to be updated?

[davidenwang]

its very unlikely for there to be brokenMonitors rows unless a user has manually called the API at this point, but if they did choose to do that I just opt to respect the setting they chose, rather than overriding the value from their "approval" setting

[github-actions]

This PR has a migration; here is the generated SQL for src/sentry/migrations/0743_backfill_broken_monitor_notification_setting_option.py ()

--
-- Raw Python operation
--
-- THIS OPERATION CANNOT BE WRITTEN AS SQL