fix(seer): Validate unvalidated coding agent org option values

[srest2021]

There are currently 2 rows in prod for the org option sentry:seer_default_coding_agent that have unvalidated values (ie, "cursor" instead of "cursor_background_agent"). We want coding agent values to match the allowed values for automation handoff target. This is a low risk migration on org options that are currently only used in UI that is feature-flagged for internal use.

Followup PR that adds validation: #111697

[github-actions]

This PR has a migration; here is the generated SQL for src/sentry/migrations/1058_normalize_coding_agent_option_aliases.py

for 1058_normalize_coding_agent_option_aliases in sentry

--
-- Raw Python operation
--
-- THIS OPERATION CANNOT BE WRITTEN AS SQL

[github-actions]

This PR has a migration; here is the generated SQL for src/sentry/migrations/1059_normalize_coding_agent_option_aliases.py

for 1059_normalize_coding_agent_option_aliases in sentry

--
-- Raw Python operation
--
-- THIS OPERATION CANNOT BE WRITTEN AS SQL

[github-actions]

Backend Test Failures

Failures on 1773dc9 in this run:

tests/sentry/integrations/api/endpoints/test_organization_repository_details.py::OrganizationRepositoryGetTest::test_get_repository_expand_settings_no_settings_exist — log

[gw0] linux -- Python 3.13.1 /home/runner/work/sentry/sentry/.venv/bin/python3
tests/sentry/integrations/api/endpoints/test_organization_repository_details.py:91: in test_get_repository_expand_settings_no_settings_exist
    assert response.data["settings"]["codeReviewTriggers"] == [
E   AssertionError: assert ['on_ready_for_review'] == ['on_ready_fo...n_new_commit']
E     
E     Right contains one more item: 'on_new_commit'
E     
E     Full diff:
E       [
E           'on_ready_for_review',
E     -     'on_new_commit',
E       ]

[sentry]

Bug: The migration updates OrganizationOption values but fails to invalidate the cache because it uses a historical model, which bypasses the post_save signal that triggers cache reloading.
_{Severity: LOW}

Suggested Fix

After saving the updated row inside the loop, add an explicit call to OrganizationOption.objects.reload_cache(row.organization_id, "migrate_coding_agent_alias") to manually invalidate the cache, since the post_save signal will not fire for the historical model.

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/migrations/1059_normalize_coding_agent_option_aliases.py#L37-L38

Potential issue: The database migration updates `OrganizationOption` rows directly using
`row.save(update_fields=["value"])` on a historical model instance. In Django
migrations, historical models do not trigger signals like `post_save`. The
`OrganizationOptionManager` relies on this signal to call `reload_cache()` for cache
invalidation. Because the signal is bypassed, the Redis and in-memory caches are not
updated, causing them to serve stale option values. The stale data will persist until
the cache's time-to-live (TTL) expires or the process is restarted.

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

[github-actions]

Backend Test Failures

Failures on bccc78d in this run:

tests/sentry/integrations/api/endpoints/test_organization_repository_details.py::OrganizationRepositoryGetTest::test_get_repository_expand_settings_no_settings_exist — log

[gw0] linux -- Python 3.13.1 /home/runner/work/sentry/sentry/.venv/bin/python3
tests/sentry/integrations/api/endpoints/test_organization_repository_details.py:91: in test_get_repository_expand_settings_no_settings_exist
    assert response.data["settings"]["codeReviewTriggers"] == [
E   AssertionError: assert ['on_ready_for_review'] == ['on_ready_fo...n_new_commit']
E     
E     Right contains one more item: 'on_new_commit'
E     
E     Full diff:
E       [
E           'on_ready_for_review',
E     -     'on_new_commit',
E       ]