DataCollection phase 2: migrate OpenTelemetry and logging integrations

Part of #5420. Phase 2 — consumer migration.

Migrate remaining integrations to the resolved config:

- `src/Sentry.OpenTelemetry/SentrySpanProcessor.cs` — db/messaging attribute passthrough (`db.statement`-equivalents → `DatabaseQueryData`; messaging attrs → `Queues` where applicable).
- `src/Sentry.Serilog/SentrySinkExtensions.cs:20,255` — `sendDefaultPii` sink parameter (keep mapping to the legacy option until the major; document).
- `src/Sentry.NLog/SentryTarget.cs:490-502` — user layouts → these are user-*configured* (explicit), so per spec they are NOT gated; confirm and add a test locking that in.
- `src/Sentry.Extensions.Logging` — anything reading `SendDefaultPii` via options binding.

Start with src/Sentry.OpenTelemetry/SentrySpanProcessor.cs, src/Sentry.Serilog/SentrySinkExtensions.cs, src/Sentry.NLog/SentryTarget.cs, and the SendDefaultPii handling in src/Sentry.Extensions.Logging. Trace each integration's resolved-config and options-binding paths, then verify database and messaging attributes, the Serilog legacy mapping, and the NLog user-layout behavior. Done means the remaining integrations follow the phase 2 specification and the NLog behavior has a locking test.

Written by the indexing model from the issue text.