Support sending User Feedback without errors/exceptions

[jamescrosswell]

Resolves #3605:

• Support for Feedback Events #3605

Related

• Updated docs to use the new Feedback APIs sentry-docs#12846

Example

[bruno-garcia]

Adding @aliu39 and @billyvg from the Replay team for review

[bruno-garcia]

Nice, we can use this to create a built-in Widget like @armcknight built for iOS

Or use bindings to use the native one. But with a MAUI implementation means we have it also on Windows and macOS

[bruno-garcia]

I find this odd. Are we trying to find a way to attach the feedback to the event somehow?
Could the feedback inherit from SentryEvent instead?

[jamescrosswell]

Not without changing all the other SDKs. This is just how the spec says we should be doing it.

[codecat]

Can there be an Action<Scope> configureScope parameter on CaptureFeedback? The documentation even says:

In the following example we use the scope callback parameter that is available for all capture methods to attach a level and a tag to only one specific error:

[jamescrosswell]

Can there be an Action<Scope> configureScope parameter on CaptureFeedback? The documentation even says:

That particular example shows the CaptureException method... but yes, those docs do say the scope can be passed on all capture methods - so we should probably add this.

It's really just a convenience. As a workaround, in the meantime, the same can be achieved by:

        using (var scopeTracker = SentrySdk.PushScope())
        {
            SentrySdk.ConfigureScope(s =>
            {
                s.SetTag("my-tag", "my value");
                s.User = new SentryUser
                {
                    Id = "42",
                    Email = "[email protected]"
                };
            });
            var feedback = new SentryFeedback(message, contactEmail, name);
            SentrySdk.CaptureFeedback(feedback, hint: hint);
        }

Note that the temporary local scope gets popped when scopeTracker gets disposed above... so important to dispose of it before creating other events that you don't want that scope applied to.