Rename sendFeedback to captureFeedback & enhance it

[billyvg]

We want to deprecate captureUserFeedback, and instead have a new API captureFeedback that users can use instead.

This will send to the new feedback API, and allow to optionally define an event id that should be assigned to the feedback. This API will also apply scope etc. to the feedback event.

We will keep the old captureUserFeedback API for v8, as the new API will require a newer self-hosted version. Eventually, only captureFeedback will remain (~in v9 or beyond).

• This ticket is requesting context for the old crash modal, but is related: User Feedback Feature Request: Custom context #10916
• Attachments: Add attachments to user feedback sentry#49946

[bruno-garcia]

Worth noting whatever we're doing here makes sense to become part of the protocol extending our current one. That's going to be eventually be built in many SDKs (in particular those with a UI like mobile and desktop).

This means updating this document: https://develop.sentry.dev/sdk/features/#user-feedback

[mydea]

Is there any reason to still use captureUserFeedback, I wonder? 🤔

[bruno-garcia]

From @lforst

Why is name a required property in captureUserFeedback()?
It is also not clear what name is supposed to be. Is it the name of the feature that someone gives feedback on, or is it the user name? I know now that it is the latter but maybe we can come up with a better identifier (or at least add JSDoc).
Having to provide and event_id is a bit annoying. We are getting rid of that right?
Why is it comments and not comment ? Alternatively I think we could call this feedback maybe?