fix(seer settings): Fix the automated_run_stopping_point save issue

[Mihir-Mavalankar]

PR details

• Fix to make sure change to "Where should Seer Stop" persists. Added getData: () => ({}) to the automatedRunStoppingPointField to prevent the Form from including this field in its auto-save payload to the Project API. This fixes the bug where the field's custom onChange handler correctly saved to the Seer Preferences API, but the Form also tried to save it to the Project API (which doesn't support this field), creating a false success message while the setting never persisted.
• More context: https://sentry.slack.com/archives/C09QCAEA0DR/p1763404095142179
• The fix is to not store it in Project API but just store it in Seer Preferences API.
• Not super sure on this one. Apparently Claude says this bug was there even before the triage-signals changes.

[Mihir-Mavalankar]

I ran this query on redash and looks like most projects are either RCA(current default) or solution(previous default) - https://redash.getsentry.net/queries/9941/source
If this was always a bug this makes sense but not sure how the orgs that don't have RCA and solution changed it.

[roaga]

i'm not really sure how these settings components work, maybe somebody else can review

[jennmueng]

yeah, this makes sense, roughly, but like rohan said I have no context either

[scttcper]

should be okay for now