feat(http): [Data Collection 12] Apply query parameter policy

[adinauer]

PR Stack (Data Collection)

• feat(core): Data Collection #5759
• feat(core): [Data Collection 1] Add configuration types #5760
• feat(core): [Data Collection 2] Expose SentryOptions API #5761
• feat(core): [Data Collection 3] Add policy resolver #5799
• feat(graphql): [Data Collection 4] Apply GraphQL policies #5800
• feat(database): [Data Collection 5] Apply query policy #5801
• feat(spring): [Data Collection 6] Apply incoming request body policy #5802
• feat(apollo): [Data Collection 7] Apply incoming response body policy #5803
• feat(apollo): [Data Collection 8] Apply outgoing request body policy #5804
• feat(graphql): [Data Collection 9] Apply outgoing response body policy #5805
• feat(http): [Data Collection 10] Apply request header policy #5806
• feat(http): [Data Collection 11] Apply response header policy #5807
• feat(http): [Data Collection 12] Apply query parameter policy #5810
• feat(http): [Data Collection 13] Apply cookie collection policy #5811
• feat(user): [Data Collection 14] Apply user information policy #5812

---

📜 Description

Apply the query-parameter Data Collection policy to automatic HTTP request data, spans, breadcrumbs, and failed-request events.

The policy is used by Servlet, Spring MVC/WebFlux, OpenTelemetry, OkHttp, Ktor, Apollo 2/3/4, OpenFeign, RestTemplate, and WebClient. Explicit Data Collection supports off, deny-list, and allow-list behavior. Built-in sensitive parameter names are always filtered, including when allow-listed. Encoded parameter names are decoded for matching while the original query encoding is retained.

When Data Collection is absent, integrations continue to attach raw query values as before.

💡 Motivation and Context

Query strings were collected automatically without a dedicated privacy control. This wires the existing dataCollection.queryParams option across Java HTTP integration paths while preserving the legacy bridge for applications that have not configured Data Collection.

Refs #5666

💚 How did you test it?

• ./gradlew spotlessApply apiDump
• ./gradlew :sentry:apiCheck
• Core resolver, URL, and query-filter tests
• Servlet and OpenTelemetry query tests
• OkHttp query integration test
• Full Ktor, Apollo 2/3/4, OpenFeign, Spring, Spring Jakarta, and Spring 7 test suites
• git diff --check

📝 Checklist

• I added GH Issue ID & Linear ID
• I added tests to verify the changes.
• No new PII added or SDK only sends newly added PII if sendDefaultPII is enabled.
• I updated the docs if needed.
• I updated the wizard if needed.
• Review from the native team if needed.
• No breaking change or entry added to the changelog.
• No breaking change for hybrid SDKs or communicated to hybrid SDKs.
• Public API changes reviewed by another Mobile SDK team member or implemented according to the develop docs spec.

🔮 Next steps

Migrate cookie collection and complete the remaining Data Collection configuration and integration work.

#skip-changelog

⚠️ Merge this PR using a merge commit (not squash). Only the collection branch is squash-merged into main.

[github-actions]

	Messages
📖	Do not forget to update Sentry-docs with your feature once the pull request gets approved.

Generated by 🚫 dangerJS against d9a1422

[sentry]

📲 Install Builds

Android

🔗 App Name	App ID	Version	Configuration
SDK Size	io.sentry.tests.size	8.48.0 (1)	release

⚙️ sentry-android Build Distribution Settings

[github-actions]

Performance metrics 🚀

	Plain	With Sentry	Diff
Startup time	319.94 ms	371.16 ms	51.22 ms
Size	0 B	0 B	0 B