DataCollection phase 2: migrate Sentry.Extensions.AI (GenAI)

Part of #5420. Phase 2 — consumer migration.

Migrate `Sentry.Extensions.AI` to `GenAI.Inputs` / `GenAI.Outputs`:

- Fold `SentryAIOptions.RecordInputs` / `RecordOutputs` (`src/Sentry.Extensions.AI/SentryAIOptions.cs:32,38`) into the resolved layer — integration-level options take precedence over global `DataCollection` when explicitly set.
- `SentryAISpanEnricher.cs:30-36` (request messages), `:126-143` (response text, tool calls) — read the resolved values.
- **Fix ungated capture**: `SentryInstrumentedFunction.cs:55` (`gen_ai.tool.input`) and `:22` (`gen_ai.tool.output`) currently bypass `RecordInputs`/`RecordOutputs` entirely.

JS references: getsentry/sentry-javascript#21247, #21287 (AI utils / genAI spans / MCP migrations).

Start with SentryAIOptions.cs at lines 32 and 38, then trace the resolved DataCollection layer and read SentryAISpanEnricher.cs at lines 30-36 and 126-143. Inspect SentryInstrumentedFunction.cs at lines 22 and 55 for the ungated tool attributes; done means the migration uses the resolved values and those captures follow the input/output settings.

Written by the indexing model from the issue text.