feat(issue-details): Add universal copy hotkey

[jennmueng]

As per discussed, we're adding a hotkey cmd+option+c / ctrl+alt+c to copy the issue & relevant content as markdown for LLM prompts.

There's no discoverable button right now, we will follow up on that, but right now we'll put it behind a hotkey that's just commonly used for AI use cases

Includes Issue summary & autofix when present

Example of a copy:

# ValidationError: 4 validation errors for DetectAnomaliesRequest

**Issue ID:** 5028696400
**Project:** seer
**Date:** 3/12/2025, 2:33:49 PM

## Tags

- **browser:** Python Requests 2.32
- **browser.name:** Python Requests
- **environment:** production
- **handled:** yes
- **level:** error
- **mechanism:** generic
- **organization_id:** 18005
- **project_id:** 34925
- **release:** 40a6e10494c312da663ec9c04e713977e82dd844
- **runtime:** CPython 3.11.0
- **runtime.name:** CPython
- **server_name:** seer-web-autofix-production-canary-5f77558cf6-bcv4f
- **transaction:** app.summarize_issue_endpoint
- **url:** http://seer-web-autofix/v1/automation/summarize/issue
- **user:** ...

## Exception

### Exception 1
**Type:** ValidationError
**Value:** 1 validation error for SummarizeIssueRequest
issue.events.0.tags.0.value
  Input should be a valid string [type=string_type, input_value=None, input_type=NoneType]
    For further information visit https://errors.pydantic.dev/2.6/v/string_type

#### Stacktrace

\```
 wrapper in seer/json_api.py [Line 131, column null] (In app)
            if not isinstance(data, dict):
                sentry_sdk.capture_message(f"Data is not an object: {type(data)}")
                raise BadRequest("Data is not an object")

            try:
                result: BaseModel = implementation(request_annotation.model_validate(data))  <-- SUSPECT LINE
            except ValidationError as e:
                capture_alert(data)
                sentry_sdk.capture_exception(e)
                raise BadRequest(str(e))

---
Variable values at the time of the exception:
{
  "auth_header": "[Filtered]",
  "config": "[Filtered]",
  "data": {
    "connected_issues": [],
    "group_id": "4190519356",
    "issue": {
      "events": [
       ...
      ]
    }
  }
}
\```

Pull Request Overview

This PR adds a universal copy hotkey (cmd/ctrl+alt+c) to copy issue details as Markdown for LLM prompts. Key changes include the implementation of the new hook (useCopyIssueDetails) in the issue details view, accompanying tests to validate the functionality, and minor updates to autofix utility functions and group summary interfaces to support the feature.

Reviewed Changes

Copilot reviewed 7 out of 7 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
static/app/views/issueDetails/streamline/hooks/useCopyIssueDetails.tsx	Adds a new hook to copy issue details as Markdown using a hotkey
static/app/views/issueDetails/streamline/hooks/useCopyIssueDetails.spec.tsx	Implements tests for the copy functionality and Markdown formatting
static/app/components/events/autofix/utils.tsx	Updates helper functions for formatting autofix-related texts
static/app/components/group/groupSummary.tsx	Exports GroupSummaryData and adds a corresponding hook for summary data retrieval
static/app/components/events/autofix/autofixSolution.tsx	Enhances the CopyToClipboardButton with a title for better accessibility
static/app/views/issueDetails/groupEventDetails/groupEventDetailsContent.tsx	Integrates the new useCopyIssueDetails hook into the issue details view
static/app/components/group/groupSummaryWithAutofix.tsx	Removes redundant helper functions in favor of using centralized utility functions

Comments suppressed due to low confidence (1)

static/app/views/issueDetails/streamline/hooks/useCopyIssueDetails.tsx:145

• Consider checking for the existence of navigator.clipboard before calling writeText to safeguard against runtime errors in environments where the Clipboard API may be unsupported or unavailable.

navigator.clipboard.writeText(text)

[roaga]

I think this should stop it. Query can still run if refetch is used anywhere, but I think we're good?

[jennmueng]

tested locally... it doesn't call it

[roggenkemper]

just to check my understanding - this is being used to get the group summary if it exists already, but won't create a new summary if one doesn't exist (so we don't need any checks around it)

[jennmueng]

yep, that is the intent and my understanding of how this hook works, other than just not rendering that hook, if we disable it via a check it'll be passing a false to enabled anyways, but this is always false

[scttcper]

does this need to be mocked like this? Doesn't make sense to reimplement the entire thing

[scttcper]

this should be an import at the top of the document and use jest.mocked(issueAndEventToMarkdown) if you need the types

[scttcper]

same here, import normally

[scttcper]

is this just testing the mock above? somewhat confused

[scttcper]

this should be in its own useEffect if you want to display an error