fix(aci milestone 3): updates to dual writing data conditions

[mifu67]

When dual writing AlertRuleTriggers to the ACI tables, we must create 2 data conditions:

1. The "detector trigger," which compares against the trigger threshold value and returns a DetectorPriorityLevel as its condition result
2. The "action filter," which checks the detector status and returns True as its condition result. Each of these "action filters" has its own DataConditionGroup as well, which is linked back to the legacy alert rule's associated workflow.

Implement this paradigm. Also add logic to automatically set a resolve threshold if it's not set by the user on the legacy alert rule.

[codecov]

❌ 1 Tests Failed:

Tests completed	Failed	Passed	Skipped
23481	1	23480	272

View the top 1 failed tests by shortest run time

tests.snuba.tagstore.test_tagstore_backend.TagStorageTest::test_get_group_tag_key_generic

Stack Traces | 7.86s run time

#x1B[1m#x1B[31mtests/conftest.py#x1B[0m:32: in unclosed_files
    assert frozenset(psutil.Process().open_files()) == fds
#x1B[1m#x1B[31mE   AssertionError: assert frozenset({po...flags=32768)}) == frozenset()#x1B[0m
#x1B[1m#x1B[31mE     #x1B[0m
#x1B[1m#x1B[31mE     Extra items in the left set:#x1B[0m
#x1B[1m#x1B[31mE     popenfile(path='.../sentry/sentry/.venv/lib/python3.12....../site-packages/certifi/cacert.pem', fd=47, position=155648, mode='r', flags=32768)#x1B[0m
#x1B[1m#x1B[31mE     #x1B[0m
#x1B[1m#x1B[31mE     Full diff:#x1B[0m
#x1B[1m#x1B[31mE     - frozenset()#x1B[0m
#x1B[1m#x1B[31mE     ?           ^#x1B[0m
#x1B[1m#x1B[31mE     + frozenset({#x1B[0m
#x1B[1m#x1B[31mE     ?           ^#x1B[0m
#x1B[1m#x1B[31mE     +     popenfile(path='.../sentry/sentry/.venv/lib/python3.12....../site-packages/certifi/cacert.pem', fd=47, position=155648, mode='r', flags=32768),#x1B[0m
#x1B[1m#x1B[31mE     + })#x1B[0m

To view more test analytics, go to the Test Analytics Dashboard
📢 Thoughts on this report? Let us know!

[saponifi3d]

🤔 it might be better for us to do the detector's data_condition migrations with the detector and the workflow's action filters in another. that's mostly just a nit to have this be a little clearer or help incase we have issues with the migration (like a workflow migrated correctly, but not a detector, we could then reuse the migrate detector method to just migrate the detector and all of it's associated conditions)

[saponifi3d]

💯