feat(feedback): shim feedback v2 to postgres so they can be queried by group_id

[aliu39]

Closes #89700

Doc describing the problem and changes: https://www.notion.so/sentry/UF-Ingest-Update-April-2025-1d78b10e4b5d80f08350fa1fbf204b24?pvs=4

Also adds userreport.py test coverage for the shim cases.

---

Testing Notes / Expected Behavior

• Submit a feedback with the JS SDK's captureFeedback function. Be sure to include an associatedEventId corresponding to an error event in the same project.

• The feedback should show up in Sentry /feedback/ page in a few seconds, at most 30s.

• Open the feedback and find the "Linked Error" section. Click on it to visit the issue/event detail.

• The feedback email, name, and message should be visible in the "User Feedback" section, and match what you see in /feedback/.

  • If it doesn't show up, there's a small chance it'll be linked by the async task, within 15min. However this should happen very rarely.
    

• No duplicate feedback should be seen in /feedback/ (wait 15min to confirm this)

• Widget feedbacks shouldn't break

[codecov]

Codecov Report

Attention: Patch coverage is 95.65217% with 5 lines in your changes missing coverage. Please review.

✅ All tests successful. No failed tests found.

Files with missing lines	Patch %	Lines
...rc/sentry/feedback/usecases/save_feedback_event.py	84.00%	4 Missing ⚠️
src/sentry/tasks/store.py	50.00%	1 Missing ⚠️

Additional details and impacted files

@@           Coverage Diff            @@
##           master   #89685    +/-   ##
========================================
  Coverage   85.27%   85.27%            
========================================
  Files       10175    10186    +11     
  Lines      574316   575110   +794     
  Branches    22625    22625            
========================================
+ Hits       489739   490453   +714     
- Misses      84030    84110    +80     
  Partials      547      547            

[ryan953]

seems reasonable to me. but i would have a hard time to know what, if anything, is missing

[sentry]

Suspect Issues

This pull request was deployed and Sentry observed the following issues:

• ‼️ TypeError: 'str' object cannot be interpreted as an integer sentry.tasks.store.save_event_feedback View Issue
• ‼️ KeyError: 'name' sentry.tasks.store.save_event_feedback View Issue
• ‼️ ValueError: invalid literal for int() with base 10: 'production' sentry.tasks.store.save_event_feedback View Issue
• ‼️ DataError: StringDataRightTruncation('value too long for type character varying(75)\n') sentry.tasks.store.save_event_feedback View Issue
• ‼️ Conflict: Feedback for this event cannot be modified. sentry.tasks.store.save_event_feedback View Issue

_{Did you find this useful? React with a 👍 or 👎}