feat(attributes): add attribute transformations

[constantinius]

Summary

• add attribute transformation documents for deprecated attributes whose replacement values need reshaping
• add deprecation._status: "transform" and deprecation.transformation references
• document how to add attribute transformations
• expose transformation references in generated JS and Python metadata

This replaces the previous migration-based approach from #454 and #455.

Contributes to TET-2369.
Closes TET-2586.

Testing

• yarn test

[linear-code]

TET-2369

TET-2586

[github-actions]

Semver Impact of This PR

🟡 Minor (new features)

📋 Changelog Preview

This is how your changes will appear in the changelog.
Entries from this PR are highlighted with a left border (blockquote style).

---

New Features ✨

Attributes

• Add attribute transformations by constantinius in #465

• Add messaging attributes by s1gr1d in #469
• Add url.same_origin (deprecated) and http.request.same_origin (replacement) attributes by Lms24 in #456
• Add db.response.status_code by s1gr1d in #462

Other

• (ai) Add granular cost attributes for cache and reasoning by vgrozdanic in #461

Internal Changes 🔧

• (ci) Stop inheriting secrets for changelog-preview by tobias-wilfert in #463

---

_{🤖 This preview updates automatically when you update the PR.}

[alexander-alderman-webb]

The types set for gen_ai.request.messages and gen_ai.response.text are inconsistent in the SDKs.
You yourself have added the litellm integration that sets a list of objects for gen_ai.response.text.
How should the suggested transformations be implemented if the source attribute does not have a consistent type?

[constantinius]

How should the suggested transformations be implemented if the source attribute does not have a consistent type?

This is true and indeed an issue. In the frontend, we have several paths to get the input/output messages, I will match them in Relay, but I think I should also mention them here in the sentry-conventions

[jjbayer]

Is the ID also what we expect the function name to be in Relay, by convention?

[constantinius]

No, this is just the ID we link to from the attribute where we want to apply the transformation.

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

Want reviews to match your repository better? Bugbot Learning can learn team-specific rules from PR activity. A team admin can enable Learning in the Cursor dashboard.

^{Reviewed by Cursor Bugbot for commit 1019ddc. Configure here.}

[constantinius]

@alexander-alderman-webb
This now also includes the transformation from various output formats we encounter across the SDK integrations.

[alexander-alderman-webb]

Well, that's not true 😅.
For example, the LangChain integration sets an array of arrays as gen_ai.response.text.

[constantinius]

@alexander-alderman-webb

For example, the LangChain integration sets an array of arrays as gen_ai.response.text.

I can't confirm this. In the testing framework I get for Python/JS LangChain only strings or array of strings across all tests. Do you have a working example?

Also, at some point we have to stop chasing wrong implementations.