chore(aci): populate legacy_rule_id and/or workflow_id in action dispatch

[cathteng]

Fully removes uses of workflow-engine-ui-links flag for issue alert firing.

We try to attach legacy_rule_id to the fake Rule's action when possible and attach the workflow_id. In downstream code we look for legacy_rule_id first to generate links, and then workflow_id. If we generate a link to the Rule, the FE will redirect it to the workflow link if the new UI feature flag is on. Otherwise the workflow is single-written and we can only generate link to the workflow.

Builds on #106048 (last one to remove the flag for issue alerts)

[cathteng]

It will actually raise Rule.DoesNotExist

[kcons]

bah, shame we're not using foreign keys or we could just do something like Rule.objects.filter(alertruleworkflow__workflow_id=workflow_id).first().

I still think single expr and first might be nice here, eg:

rule = Rule.objects.filter(
      id__in=AlertRuleWorkflow.objects.filter(workflow_id=workflow_id).values('rule_id')
 ).first()
if rule:
    label = ..
    rule_id = ...

[sentry]

Bug: The query for AlertRuleWorkflow can fetch a metric alert where rule_id is None, causing an unhandled ValueError when Rule.objects.get(id=None) is called.
_{Severity: CRITICAL}

Suggested Fix

Modify the AlertRuleWorkflow query to explicitly filter for entries related to issue alerts by adding rule_id__isnull=False. This ensures that the query only returns workflows that have a valid rule_id.

alert_rule_workflow = AlertRuleWorkflow.objects.filter(
    workflow_id=workflow_id,
    rule_id__isnull=False,
).first()

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/notifications/notification_action/types.py#L206-L212

Potential issue: The query for an `AlertRuleWorkflow` using
`.filter(workflow_id=workflow_id).first()` is non-deterministic. If a workflow is
associated with both an issue alert (`rule_id` is set) and a metric alert
(`alert_rule_id` is set), this query might return the metric alert entry where `rule_id`
is `None`. The subsequent call, `Rule.objects.get(id=alert_rule_workflow.rule_id)`, will
then execute as `Rule.objects.get(id=None)`, raising a `ValueError`. This exception is
not caught by the `except Rule.DoesNotExist` block, leading to an unhandled error.

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

[cathteng]

This raises Rule.DoesNotExist which is caught