feat(search-attributes): Add search attribute names

[nsdeschenes]

Description

Generate typed SEARCH_* constants for Sentry search names so consumers can avoid hardcoded strings, and publish the search-specific API from its own module:

import {
  ATTRIBUTE_SEARCH_METADATA,
  SEARCH_TRANSACTION,
  type AttributeSearchName,
} from '@sentry/conventions/attributes/search';

What changed

• Generate search constants, AttributeSearchName, search metadata types, and ATTRIBUTE_SEARCH_METADATA into a dedicated search.ts file instead of attributes.ts.
• Add the @sentry/conventions/attributes/search package export, build entry, and compatibility shims for older bundlers and TypeScript resolvers.
• Keep preferred search aliases as the current constants, such as SEARCH_TRANSACTION = 'transaction'.
• Continue emitting deprecated search names derived from attribute chains, marking them deprecated in favor of the preferred search alias where applicable.
• Keep current constants for attributes without an explicit search alias.
• Normalize away a leading sentry. in generated search names, so sentry.transaction and transaction produce only SEARCH_TRANSACTION = 'transaction'.
• Preserve actual storage keys in canonicalName and deprecationChain metadata without exposing duplicate _SEARCH_* constants.
• Preserve underscore distinctions so names such as ai.model_id and ai.model.id cannot collide.
• Keep ATTRIBUTE_SEARCH_METADATA keyed by search_alias.name ?? attribute.key.

Test plan

• yarn test:js — 9,224 tests pass
• yarn lint:types:js
• yarn lint:js
• yarn build:js
• Verified a runtime import from @sentry/conventions/attributes/search

[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 browser.navigation.type, move navigation.* to router.navigation.* by logaretm in #600
• Add langchain.chain.name (deprecated) in favor of gen_ai.pipeline.name by RulaKhaled in #599
• Add browser.paint.type by Lms24 in #606

Names

• Add browser.* span name and description rules by Lms24 in #607
• Add cache span name rules by Lms24 in #605

Other

• (search-attributes) Add search attribute names by nsdeschenes in #610

Internal Changes 🔧

• (descriptions) Fix http.client span description example by Lms24 in #603

---

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

[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.}

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

[mjq]

So this is pretty pedantic but could we consider flipping these?

Suggested change

	.replaceAll('_', '__')
	.replaceAll('.', '_')
	.replaceAll('_', '_')
	.replaceAll('.', '__')

. separates a level, and _ separates a multi-word name inside that level. So . is a "heavier" split than _. I think the constants read better if names stay closer together - so e.g. keep "step functions" together as SEARCH_AWS__STEP_FUNCTIONS__ACTIVITY__ARN instead of SEARCH_AWS_STEP__FUNCTIONS_ACTIVITY_ARN.

FWIW this also would make it align with Relay.

[nsdeschenes]

Sounds good to me!

[mjq]

TBH I think I'd rather handle these by putting search aliases on the attributes instead of a blanket policy here - having this enforced by the code generator feels like the wrong place compared to the model JSON 👀