Support for default fields in custom field configurations

### Problem Statement

We recently ran into the issue of descriptions not being transferred to the Jira ticket when creating one from sentry. This was caused by the fact that we have custom field configurations for our different issue types which sets a new id for the description field (so not the standard 10001 of the default field configurations).

### Solution Brainstorm

Unlike with custom fields, the description is a standard field and should be referable to by name in the API call. If this is correct, it would simply be a matter of using the field name instead of the ID in the request body.

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)*