chore(aci): roll out DELETE issue alert endpoint flag

[klochek]

No description provided.

[linear-code]

ISWF-2396 Roll out issue alert rule DELETE endpoint

[sentry]

Bug: An unexpected error during Rule deletion can cause an inconsistent state because the associated Workflow deletion is committed separately and cannot be rolled back.
_{Severity: MEDIUM}

Suggested Fix

Wrap both the Workflow and Rule deletion operations within a single, overarching atomic transaction. This ensures that both operations must succeed for the changes to be committed, preventing any potential for an inconsistent state if the Rule deletion fails unexpectedly.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent. Verify if this is a real issue. If it is, propose a fix; if not, explain why it's
not valid.

Location: src/sentry/api/endpoints/project_rule_details.py#L108-L111

Potential issue: In the `delete` method, a `Workflow` is scheduled for deletion and this
change is committed within its own atomic transaction. Subsequently, the code attempts
to delete the associated `Rule`. However, the error handling for the `Rule` deletion
only catches `DoesNotExist` exceptions. If any other unexpected exception occurs during
the `Rule` deletion, the API will return a 500 error, leaving the system in an
inconsistent state where the `Workflow` is pending deletion but the `Rule` is not.

_{Did we get this right? 👍 / 👎 to inform future reviews.}