… streaming (#23582)

With span streaming enabled (the default), `gen_ai.invoke_agent` names
follow the [agent span name
conventions](https://getsentry.github.io/sentry-conventions/names/#gen_ai-agent):
`{operation} {name}` from `gen_ai.agent.name`, `gen_ai.pipeline.name` or
`gen_ai.function_id`, otherwise `{operation}`.

In practice this only changes LangChain chain spans, and only their
prefix. They were named `chain format_prompt`, which does not lead with
the operation like every other agent span; they are now `invoke_agent
format_prompt`. The chain name itself is bounded, so it stays in the
name. A chain the SDK cannot name falls back to `invoke_agent` rather
than carrying the `unknown_chain` sentinel, the same way a missing model
is dropped in #23573.

LangGraph agent names and Vercel AI `functionId`s are unchanged in both
lifecycles — both are bounded, low-cardinality values.

The `pipeline.name` and `function_id` templates are added in
getsentry/sentry-conventions#593. LangChain still emits its chain name
on `langchain.chain.name`; moving it to `gen_ai.pipeline.name` is
tracked in
[JS-3452](https://linear.app/getsentry/issue/JS-3452/move-langchainchainname-to-gen-aipipelinename)
and should land before v11 ships, so the emitted name matches a
published template. Span names are unaffected by that move — they are
built from the local chain name, not read back off the attribute.

The other two ops in the agent rule need nothing: the SDK emits no
`gen_ai.handoff` spans, and `gen_ai.create_agent` was dropped in v11.
Neither is listed in the migration table.

The migration entry lives in `MIGRATION.md` rather than
`docs/migration/v11-end-state.md`, which was removed by #23623.

Fixes #23524

---------

Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Claude Opus 5 <noreply@anthropic.com>

Two conflicts, both in the google-genai instrumentation that develop moved under us.

packages/server-utils/src/ai/google-genai/index.ts: develop added low-cardinality
span names when span streaming is on (getsentry#23573) and dropped the captureException
calls from the instrumentation (getsentry#23024), touching the same lines where this branch
threads the chat create-time params through. Kept both: the merged apply() computes
attributeParams via mergeChatCreateParams, feeds those to extractRequestAttributes
plus addPrivateRequestAttributes, then derives model with develop's || 'unknown' and
its spanName sentinel logic.

packages/server-utils/test/ai/lib/tracing/google-genai.test.ts: add/add, develop
landed a span-names suite at the same path this branch used for the config suite.
Took develop's file whole and re-added the config suite beside it, hoisting the
shared setupClient to module scope and switching the config assertions from
spanToJSON to spanToStaticSpanJSON, since spanToJSON now returns the streamed shape
(attributes, no data).

Also updated the Cloudflare integration test. Its chat span assertion matches
attributes exhaustively with toEqual, while that scenario passes a config to
chats.create, so propagating it adds temperature, top_p and max_tokens to the chat
span. Verified the assertion fails without those three keys and passes with them.
The node suites assert per key, so they were unaffected.

Verified: @sentry/server-utils 432 tests passing (44 files), node google-genai and
google-genai-v2 integration 24 passing, cloudflare google-genai integration 1
passing, oxfmt --check, oxlint --type-aware, oxlint src --type-aware --type-check.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>