Use grouping stacktrace frames when generating a Jira ticket

### Problem Statement

When we use the Jira integration in Sentry to create tickets, the preview stacktrace it includes will use in-app frames if available. If there are no in-app frames but there _**are**_ frames used for grouping, it ignores them and simply includes the top 4-5 frames. This makes the preview unhelpful because there's no way to see context without having to go to the Sentry event and find the part of the stacktrace that is relevant.

### Solution Brainstorm

Ideally the Jira integration would cascade through different priorities for producing a preview stacktrace similar to how grouping uses different rules and levels when displaying in the portal.

1. In-app frames
2. Frames used for grouping
3. ???
4. Frames from the top

### Product Area

Issues

Start by locating the Jira integration code that builds the preview stacktrace, then trace how in-app and grouping frames are selected. Confirm the fallback order described in the issue, and consider how the existing top-frame fallback should behave. Done means the preview uses grouping frames when no in-app frames are available, while retaining the remaining fallback behavior.

Written by the indexing model from the issue text.