Improved Issue Assignment

### Problem Statement

Being able to auto assign an issues to multiple teams based off the crashing/problematic frames within a stacktrace

### Solution Brainstorm

"For what it’s worth (from a product perspective), as an engineer to me the ordering of ownership within a stacktrace is quite important (and much more significant than the ordering of the aggregate CODEOWNERS file). For example, if we have an entrypoint owned by team A and that calls into code owned by team B which errors, it would be ideal if at the very least we had consistent behavior around whether team A is auto assigned or team B is (i.e. is it assigned closer to entrypoint or to the crashing frame?). Even better if we could “assign” to both teams but I realize that doesn’t really fit Sentry’s model (we will probably develop our own workaround to ensure that both teams are at least notified via tags)."

### Product Area

Issues