Long stack trace filenames are impossible to read

### Environment

SaaS (https://sentry.io/)

### Steps to Reproduce

I have seen a number of these in the wild, this is a generated example:

Hovering over the first one:

I'm not easily able to replicate here since Go doesn't allow spaces in import paths, but spaces in these paths make the experience even worse.

### Expected Result

Users are able to see the full path when hovering and when the filenames contain spaces they are also rendered correctly.

### Actual Result

Truncated tooltips.

### Product Area

Issues

### Link

_No response_

### DSN

_No response_

### Version

_No response_

Start in Sentry's SaaS Issues interface by reproducing the long stack-trace filename shown in the attached example, including a path with spaces. Verify the hover tooltip and rendered filename behavior; done means the full path is readable and filenames containing spaces render correctly.

Written by the indexing model from the issue text.