fix(migrations): Use indexes instead of constraints to define an index (#6723)

Co-authored-by: Víctor Fernández Poyatos <victor@prowler.com>

api/src/backend/api/migrations/0007_scan_and_scan_summaries_indexes.py

@@ -16,9 +16,9 @@ class Migration(migrations.Migration):
                 name="scans_prov_state_insert_idx",
             ),
         ),
-        migrations.AddConstraint(
+        migrations.AddIndex(
             model_name="scansummary",
-            constraint=models.Index(
+            index=models.Index(
                 fields=["tenant_id", "scan_id"], name="scan_summaries_tenant_scan_idx"
             ),
         ),

api/src/backend/api/models.py

@@ -1098,16 +1098,18 @@ class ScanSummary(RowLevelSecurityProtectedModel):
                 fields=("tenant", "scan", "check_id", "service", "severity", "region"),
                 name="unique_scan_summary",
             ),
-            models.Index(
-                fields=["tenant_id", "scan_id"],
-                name="scan_summaries_tenant_scan_idx",
-            ),
             RowLevelSecurityConstraint(
                 field="tenant_id",
                 name="rls_on_%(class)s",
                 statements=["SELECT", "INSERT", "UPDATE", "DELETE"],
             ),
         ]
+        indexes = [
+            models.Index(
+                fields=["tenant_id", "scan_id"],
+                name="scan_summaries_tenant_scan_idx",
+            )
+        ]
 
     class JSONAPIMeta:
         resource_name = "scan-summaries"