ref(crons): Set all legacy MUTED monitors to simply ACTIVE (#61583)

After the clean up of moving status=muted into it's own `is_muted`
column, we would like to repurpose the disabled status for getsentry
billing related purposes.

This migration resets all MUTED status monitors to ACTIVE.

The muted state is now stored on `is_muted` and is being read from there
in the UI.

migrations_lockfile.txt

@@ -9,5 +9,5 @@ feedback: 0003_feedback_add_env
 hybridcloud: 0009_make_user_id_optional_for_slug_reservation_replica
 nodestore: 0002_nodestore_no_dictfield
 replays: 0003_add_size_to_recording_segment
-sentry: 0620_add_has_new_feedbacks_flag
+sentry: 0621_set_muted_monitors_to_active
 social_auth: 0002_default_auto_field

src/sentry/migrations/0621_set_muted_monitors_to_active.py

@@ -0,0 +1,44 @@
+# Generated by Django 3.2.23 on 2023-12-12 00:06
+
+from django.db import migrations
+
+from sentry.new_migrations.migrations import CheckedMigration
+from sentry.utils.query import RangeQuerySetWrapperWithProgressBar
+
+
+def set_muted_monitors_active(apps, schema_editor):
+    Monitor = apps.get_model("sentry", "Monitor")
+    query = Monitor.objects.filter(status=1)
+
+    # Update the legacy "MUTED" status monitors to simply be "ACTIVE". The `1`
+    # status (disabled) will be repurposed in the future for getsentry billing
+    # related purposes.
+    for monitor in RangeQuerySetWrapperWithProgressBar(query):
+        monitor.status = 0
+        monitor.save()
+
+
+class Migration(CheckedMigration):
+    # This flag is used to mark that a migration shouldn't be automatically run in production. For
+    # the most part, this should only be used for operations where it's safe to run the migration
+    # after your code has deployed. So this should not be used for most operations that alter the
+    # schema of a table.
+    # Here are some things that make sense to mark as dangerous:
+    # - Large data migrations. Typically we want these to be run manually by ops so that they can
+    #   be monitored and not block the deploy for a long period of time while they run.
+    # - Adding indexes to large tables. Since this can take a long time, we'd generally prefer to
+    #   have ops run this and not block the deploy. Note that while adding an index is a schema
+    #   change, it's completely safe to run the operation after the code has deployed.
+    is_dangerous = False
+
+    dependencies = [
+        ("sentry", "0620_add_has_new_feedbacks_flag"),
+    ]
+
+    operations = [
+        migrations.RunPython(
+            set_muted_monitors_active,
+            migrations.RunPython.noop,
+            hints={"tables": ["sentry_monitor"]},
+        ),
+    ]