ref(aci): Prefer workflow id when building alert links

[sentry-junior]

get_rule_or_workflow_id returns the legacy rule id whenever one is present. That made sense when it was added, but it also means every caller that only uses it to pick a rule link or a workflow link ends up linking to the legacy rule even when a workflow id is available.

This adds a keyword-only prefer argument (default unchanged, "legacy_rule_id"). Callers that only use the result to build a link now pass prefer="workflow_id":

• Slack footer (build_slack_footer) and Slack issue title link plus its environment lookup
• Shared messaging footer (build_footer)
• Discord title link
• AlertRuleNotification.get_notification_title

Callers where the id means something beyond a link stay on the legacy default:

• Slack block id "rule": the Slack action handler resolves it back to a Rule
• Digest record ids (event_to_record / split_rules_by_rule_workflow_id): these have to match the record's IdentifierKey
• Sentry App alert webhook payload id: an external contract

The Slack test expectations now point to /monitors/alerts/<workflow_id>/ and workflow_id= in the cases where the factory rule carries both ids.

via Kyle Consalus.

--

View Junior Session [Sentry]

[kcons]

bugbot review

[cursor]

✅ Bugbot reviewed your changes and found no new issues!

Comment @cursor review or bugbot run to trigger another review on this PR

^{Reviewed by Cursor Bugbot for commit 7ceadb9. Configure here.}