chore(seer-activity): Correct webhook url and web_url alert keys

[leeandher]

Slight update to the webhook format I noticed while drafting getsentry/sentry-docs#18588. For issues, the url is by default for the API, and we specify user facing urls as web_url.

Added web_url and corrected that for the alert section of the webhook.

[linear-code]

ISWF-2955

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 5ce235a. Configure here.}

[cursor]

Duplicate org in API URL

High Severity

The alert url passed to absolute_api_url includes an organizations/{slug}/ prefix, but that helper already builds /api/0/organizations/{slug}/…. The webhook emits a duplicated segment and a non-existent API path, so consumers treating alert.url like issue url get broken links.

 

^{Reviewed by Cursor Bugbot for commit 5ce235a. Configure here.}

[Christinarlong]

idk if this is valid or not, but we could add a test to prove/misprove this

[sentry]

Bug: The call to organization.absolute_api_url redundantly includes the organization slug in the path, creating a malformed URL.
_{Severity: HIGH}

Suggested Fix

Update the call to organization.absolute_api_url to only pass the path segment that follows the organization slug. Change the path argument from f"organizations/{organization.slug}/workflows/{workflow.id}/" to f"workflows/{workflow.id}/".

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/activity_registry/sentry_app.py#L151-L153

Potential issue: The `organization.absolute_api_url` function is called with a path that
includes `organizations/{organization.slug}/`. However, the function itself is designed
to prepend `/api/0/organizations/{slug}/` to the provided path. This results in a
duplicated path segment, creating a malformed URL like
`/api/0/organizations/{slug}/organizations/{slug}/workflows/{workflow.id}//`. Any
webhook calls attempting to use this URL will fail with a 404 error, breaking the
notification functionality.

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

[Christinarlong]

idk if this is valid or not, but we could add a test to prove/misprove this