fix(names): Add missing gen_ai ops to span name rules - #579

…eaming (#23573)

When span streaming is enabled, gen_ai inference span names follow the
inference templates: `{operation} {model}` when a model is known,
`{operation}` when it is not. Instrumented methods always have an
operation, so the convention fallback `Generative AI model operation` is
not emitted today.

`traceLifecycle: 'static'` keeps the previous names (`chat unknown`).
Known models stay in the name in both lifecycles (`chat gpt-4`).

The inference ops the SDK emits are `gen_ai.chat`, `gen_ai.embeddings`,
`gen_ai.generate_content` and `gen_ai.rerank` — the last three were only
added to the conventions' inference rule in
[sentry-conventions#579](getsentry/sentry-conventions#579),
but the naming here is derived from the operation rather than hardcoded
per op, so they were already covered. The Vercel AI channel path never
emitted an `unknown` model sentinel, so its names were already
conformant; a test now locks that in. The SDK emits no
`gen_ai.responses` or `gen_ai.text_completion` spans.

`gen_ai.execute_tool` spans keep the tool name in their name
(`execute_tool getWeather`) — the tool name is a bounded, resolved
value, so it behaves like a known model rather than a high-cardinality
identifier. Agent ops (`gen_ai.invoke_agent`, `gen_ai.create_agent`,
`gen_ai.handoff`) are out of scope here and handled in #23582
(`JS-3409`).

Fixes #23525