Support for `captureFeedback` function

[bruno-garcia]

Description

This function is the base functionality needed to allow capturing user feedback while including tags, replay_id, trace_id, etc. It's part of the 'new user feedback' product (https://github.com/getsentry/sentry/issues/64671) that was shipped for Web. That included a built-in widget, that allows screenshot attachment, and under the hood relies on this new function that deprecates the old captureUserFeedback which required an event_id. The new function optionally takes a related event_id and will contain relevant context stand alone.

This means a new envelope format for feedback was introduced. The new Feedback product architecture has thoroughly documented by @aliu39 here:

• https://develop.sentry.dev/application/feedback-architecture/

This new function will allow outgoing feedbacks to be tied to Session Replay, which is currently Open Beta and we're working on GA:

• https://github.com/getsentry/sentry/issues/74441

The develop docs have not been added yet, but the ticket with details about it is here:

• https://github.com/getsentry/develop/issues/1206

Relates to:

• https://github.com/getsentry/sentry-react-native/issues/3859
• https://github.com/getsentry/sentry-java/issues/3599
• https://github.com/getsentry/sentry-go/issues/842
• https://github.com/getsentry/sentry-dart/issues/1593
• https://github.com/getsentry/sentry-javascript/issues/10953
• https://github.com/getsentry/sentry/issues/68481 - trace_id allows the product to show all related telemetry collected during that trace

[bruno-garcia]

Hey @armcknight this would be the base needed for a widget. Is this something you could help us with?

[bruno-garcia]

@armcknight we can close this one, right?

[philipphofmann]

@armcknight, can we close this?

[armcknight]

Sorry I missed these mentions. No, there are plenty of outstanding tasks here.

[bruno-garcia]

Can we rename the issue? Right now it's _Support for captureFeedback function_ and I thin that part is complete