[grouping] Improve 'Event Grouping Information' section on issue details page

[lobsterkatie]

Bugs:

• Confusing language about values which aren't used in grouping: [grouping info] Fix confusing language re: fallbacks taking precedence #61276
• Broken formatting of client fingerprint values [grouping info] Fix formatting of client-side fingerprint values #72290
• Non-contributing client fingerprint showing in Contributing Values view [grouping info] Hide client fingerprint in Contributing Values view if it doesn't contribute #72291
• Inconsistent parameterization [grouping info] Inconsistent parameterization of exception.value values (maybe others, too?) #72294
• Misleading hints about in-app vs full stacktrace variants [grouping info] Inconsistent/incorrect messaging about in-app vs full stacktrace #72333
• Unclear correspondence between rule descriptions and rule contents [grouping info] Description of rule used doesn't always match rule #72435
• Incorrect description of built-in fingerprints taking precedence [grouping info] Built-in fingerprint listed as custom in precedence comment #78745
• Stacktrace is upside down [grouping info] Reverse stacktrace frame order #81933

Improvements:

• Show underlying reason why values aren't used [grouping info] Show real reason for exclusion #61280
• Attempt to detect (and flag) when users are using the wrong one of ^- and v- in their rules [grouping] Try to detect backwards usage of v- and ^- #61377
• Show source of rule used (user/built-in) [grouping info] Differentiate between user rules and our rules #72251
• Highlight contributing values in All Values view [grouping info] Color-code or highlight to show which values contribute #72288
• Consistently show hints about ignoring [grouping info] Always show reason for ignoring client fingerprint #72289
• Clarify how the {{ default }} fingerprint value interacts with other fingerprint values [grouping info] Explain better what's happening when fingerprint includes {{ default }} #72293
• Name things in understandable ways [grouping info] Name things in more recognizable ways #72332
• Remove redundant type entry [grouping info] Remove type field from UI #72331
• Small headings fixes [grouping info] Clean up headings #72343
• Contributing frame gets hidden [grouping info] Contributing frame hidden when showing all values #74977
• Make main and grouping info stacktraces correspond better [grouping info] Grouping info stacktrace hard to match to main stacktrace #74984

[getsantry]

Routing to @getsentry/product-owners-issues for triage ⏲️

[armenzg]

In the case of the customer we were investigating, the direction the carrots was not incorrect.

[armenzg]

@lobsterkatie we have the other tickets; do you still want to keep this one?

[lobsterkatie]

I think it's nice to have some place to gather all of the related tickets, so if we ever decide to tackle this, we know all the different problems we need to fix.