feat(replays): Define replayId as a deprecated attribute

[mjq]

Description

SDKs currently send replayId on spans, but we'd like to standardize on sentry.replay_id (already defined and in use for other telemetry types). Marking it as deprecated lets the product transparently query either name and return results for either attribute.

PR Checklist

• I have run yarn test and verified that the tests pass.
• I have run yarn generate to generate and format code and docs.

[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 ✨

• (replays) Define replayId as a deprecated attribute by mjq in #401

---

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

[Lms24]

nit: we can link to this PR for reference

Suggested change

	"version": "next"
	"version": "next"
	"prs": [401]

[mjq]

Double-checking - is this necessary? I used to think it was, but it looks like it's actually handled automatically by the generation script (the one that rewrites next into the version number).

sentry-conventions/scripts/generate_attribute_changelog.ts

Lines 289 to 292 in 6ff072d

	function extractPrNumber(message: string): number | undefined {
	const match = message.match(/\(#(\d+)\)\s*$/);
	return match ? Number(match[1]) : undefined;
	}

sentry-conventions/scripts/generate_attribute_changelog.ts

Lines 116 to 140 in 6ff072d

	// Extract PR numbers from all commits in this version (respecting ignore list)
	const prs = new Set<number>();
	for (const commit of commits) {
	if (isCommitIgnored(commit.hash)) {
	const pr = extractPrNumber(commit.message);
	if (pr !== undefined) skippedPrs.add(pr);
	continue;
	}
	const pr = extractPrNumber(commit.message);
	if (pr !== undefined) {
	prs.add(pr);
	}
	}
	// Don't create empty 'next' entries — commits without PR numbers are
	// infrastructure/tooling changes, not real attribute changes
	if (to === 'next' && prs.size === 0) {
	continue;
	}
	const entry: ChangelogEntry = { version: to };
	if (prs.size > 0) {
	entry.prs = Array.from(prs).sort((a, b) => a - b);
	}
	changelog.push(entry);

[Lms24]

The generate_attribute_changelog.ts script currently isn't called at release time. AFAIK, this was meant to run manually once but not repeatedly (will check and delete if so). For releases, we only the bump_attribute_changelog.ts script. But this one only does the "next" to {new_version} conversion but doesn't add the PR number. Something we should fix! I'll look into this.

For this PR, no strong feelings. Feel free to merge with or without the PR reference!

[Lms24]

I remembered why generate_attribute_changelog isn't called at release: It takes 5+ minutes locally to run because it looks at every attribute x every single version of conventions to "backfill" PRs and version data from git history. I think we can make this a bit faster for releases by limiting it to "next" entries.