Include Sentry issue id in PR comments

### Problem Statement

Sentry comments on our PRs with related existing sentry issues

This is quite helpful, and usually correct.
When having identified the correct sentry issue that we are trying to fix, we can resolve it by writing "Fixes SENTRY-ISSUE-ID" in the PR body, but in order to get this id, you have to actually navigate to Sentry, which feels unnecessary – Sentry clearly already knows which issue I want to solve 🤓

### Solution Brainstorm

In the table of potentially relevant existing sentry issues, include the ID that we need to paste in the PR body in order to solve that issue

### Product Area

Issues

We want to define a set of [lightweight metrics]() that SDKs can automatically collect for e.g. framework, language or platform, focusing only on signals that **do NOT overlap with Tracing**. Ideally these metrics should give a quick sense of app or runtime health, … while deeper investigation will still rely on traces or profiles.

Examples**:**

* Node.js runtime metrics (e.g., event loop delay, heap usage)
* Prisma-related metrics in Next.js
* Mobile CPU / memory usage to help surface potential ANRs or app hangs

---

**Candidate Metrics (add more below)**

* …

*(please also add ideas, questions or examples in comments)*

Locate the implementation that builds the table of potentially relevant existing Sentry issues in PR comments, then inspect any tests covering that output. The work is done when each listed issue includes the ID needed for a PR body such as “Fixes SENTRY-ISSUE-ID”.

Written by the indexing model from the issue text.