migration(shared-views): Add migration to delete default views (#90853)

As part of the shared views feature launch, we would like to remove all
of the default views that have been created before, as this pollutes the
"All View" page with a lot of duplicate entries.

The default views to be deleted have the following conditions: 

1. The name of the view is "Prioritized" 
2. The query of the view is `is:unresolved issue.priority:[high,
medium]`
3. ~This view is the org member's _only_ view~

Author: MichaelSun48

migrations_lockfile.txt

@@ -21,7 +21,7 @@ remote_subscriptions: 0003_drop_remote_subscription
 
 replays: 0004_index_together
 
-sentry: 0880_orgauthtoken_bigint
+sentry: 0881_delete_single_prioritized_groupsearchviews
 
 social_auth: 0002_default_auto_field
 

src/sentry/migrations/0881_delete_single_prioritized_groupsearchviews.py

@@ -0,0 +1,50 @@
+# Generated by Django 5.1.7 on 2025-05-02 17:28
+
+from django.db import migrations
+from django.db.backends.base.schema import BaseDatabaseSchemaEditor
+from django.db.migrations.state import StateApps
+from django.db.models import Q
+
+from sentry.new_migrations.migrations import CheckedMigration
+from sentry.utils.query import RangeQuerySetWrapperWithProgressBar
+
+
+def delete_single_prioritized_groupsearchviews(
+    apps: StateApps, schema_editor: BaseDatabaseSchemaEditor
+) -> None:
+    GroupSearchView = apps.get_model("sentry", "GroupSearchView")
+
+    target_query_set = GroupSearchView.objects.filter(
+        Q(name="Prioritized") & Q(query="is:unresolved issue.priority:[high, medium]")
+    )
+
+    for gsv in RangeQuerySetWrapperWithProgressBar(target_query_set):
+        gsv.delete()
+
+
+class Migration(CheckedMigration):
+    # This flag is used to mark that a migration shouldn't be automatically run in production.
+    # 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 post deployment:
+    # - Large data migrations. Typically we want these to be run manually 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
+    #   run this outside deployments so that we don't block them. Note that while adding an index
+    #   is a schema change, it's completely safe to run the operation after the code has deployed.
+    # Once deployed, run these manually via: https://develop.sentry.dev/database-migrations/#migration-deployment
+
+    is_post_deployment = True
+
+    dependencies = [
+        ("sentry", "0880_orgauthtoken_bigint"),
+    ]
+
+    operations = [
+        migrations.RunPython(
+            delete_single_prioritized_groupsearchviews,
+            reverse_code=migrations.RunPython.noop,
+            hints={"tables": ["sentry_groupsearchview"]},
+        ),
+    ]