[giortzisg]

Description

This PR changes the stacktrace parsing behavior to throw away confusing sentry.Recover frames being reported. In active panics the frames would consist of a runtime.gopanic frame which indicates the boundary of where the panic originated from. In those cases the SDK should throw away the rest of the frames and keep only the panic origin.

Issues

• resolves: Stack trace has confusing top frame when using sentry.CurrentHub().Recover(err) #741
• resolves: GO-149

Changelog Entry Instructions

To add a custom changelog entry, uncomment the section above. Supports:

• Single entry: just write text
• Multiple entries: use bullet points
• Nested bullets: indent 4+ spaces

For more details: custom changelog entries

Reminders

• Add GH Issue ID & Linear ID
• PR title should use conventional commit style (feat:, fix:, ref:, meta:)
• For external contributors: CONTRIBUTING.md, Sentry SDK development docs, Discord community

Changelog Entry

• fix: skip recover frames on panic. This changes stacktrace behavior for captured panics, removing sentry.Recover frames to focus on the actual panic frames. The changes might affect issue grouping.

[linear-code]

GO-149