ref(hc): OrganizationMember.user_is_active backfill (#50019)

Backfills new column that allows User is active queries on
OrganizationMember

migrations_lockfile.txt

@@ -6,5 +6,5 @@ To resolve this, rebase against latest master and regenerate your migration. Thi
 will then be regenerated, and you should be able to merge without conflicts.
 
 nodestore: 0002_nodestore_no_dictfield
-sentry: 0472_delete_past_organization_mappings
+sentry: 0473_backfill_organization_member_is_active
 social_auth: 0001_initial

src/sentry/migrations/0473_backfill_organization_member_is_active.py

@@ -0,0 +1,41 @@
+# Generated by Django 2.2.28 on 2023-04-25 20:25
+
+from django.db import migrations
+
+from sentry.new_migrations.migrations import CheckedMigration
+from sentry.utils.query import RangeQuerySetWrapperWithProgressBar
+
+
+def backfill_om_is_active(apps, schema_editor):
+    OrganizationMember = apps.get_model("sentry", "OrganizationMember")
+    for om in RangeQuerySetWrapperWithProgressBar(OrganizationMember.objects.all()):
+        # Default is true, so update only on False.
+        if not om.user.is_active:
+            om.user_is_active = False
+            om.save(update_fields=["user_is_active"])
+
+
+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 = True
+
+    dependencies = [
+        ("sentry", "0472_delete_past_organization_mappings"),
+    ]
+
+    operations = [
+        migrations.RunPython(
+            backfill_om_is_active,
+            reverse_code=migrations.RunPython.noop,
+            hints={"tables": ["sentry_organizationmember"]},
+        ),
+    ]