Revitalizing the "culprit" field docs updates #16016
Description
Currently, the "Culprit" field in the Issue List and Detail views is a deprecated legacy component. Because the logic hasn't been updated in years, it often defaults to generic stack trace frames (e.g., middleware.js or <anonymous>) which provide zero signal to the user during triage.
Furthermore, a technical limitation in our server-side tagging (200-character limit on URL tags) means that for complex web applications, we are completely losing the "Location" context of an error.
The result: Users are forced to click into every issue to find out where it happened, increasing Time to Resolution (TTR) and causing "triage fatigue."