DataCollection phase 2: migrate Sentry.AspNetCore

Part of #5420. Phase 2 — behavior-neutral consumer migration.

Migrate `Sentry.AspNetCore` to the resolved config:

- `src/Sentry.AspNetCore/ScopeExtensions.cs:40-52` — user factory gating → `UserInfo`.
- `:140-151` — cookie/header capture → `Cookies` / `HttpHeaders.Request` behaviors (shared filter utility).
- `:155-159` — `REMOTE_ADDR` client IP → `UserInfo`.
- `:136` — query string → `UrlQueryParams` behavior.
- `:170-186` + `RequestBodyExtractionDispatcher` — body capture → `HttpBodies` flag for *whether*; `MaxRequestBodySize` keeps governing *size* (integration option takes precedence).
- `src/Sentry.AspNetCore.Grpc/ProtobufRequestExtractionDispatcher.cs` — same gating for protobuf bodies.
- `src/Sentry.OpenTelemetry/AspNetCoreEnricher.cs:11-20` — user factory gating → `UserInfo`.

Start with the resolved configuration and the listed ranges in src/Sentry.AspNetCore/ScopeExtensions.cs, then inspect RequestBodyExtractionDispatcher and src/Sentry.AspNetCore.Grpc/ProtobufRequestExtractionDispatcher.cs. Also review src/Sentry.OpenTelemetry/AspNetCoreEnricher.cs:11-20. Done means each migration uses the specified behavior flags, MaxRequestBodySize precedence remains intact, and behavior stays neutral.

Written by the indexing model from the issue text.