ref(aiohttp): Move crumbs to integration

[sentrivana]

Description

Create HTTP client breadcrumbs directly in the aiohttp integration instead of using maybe_create_breadcrumbs_from_span.

👀 Best reviewed with Hide whitespace on.

This turned out to be a bigger change than expected:

• Breadcrumb data should be on par with what we're sending now. When we were taking it from the span, we had all the data readily available when we needed to create the breadcrumb. When moving the logic to the integration, we now need to remember information from the start request hook because it's not available in the finish request hook, where we create the breadcrumb now. (We need to create the breadcrumb at the end, because it contains stuff like HTTP status code.)
• Breadcrumb data should be subject to PII filtering from send_default_pii/data_collection. So e.g. if parts of the query have been redacted on a span, they should not appear verbatim in the breadcrumb.
• Since the PII redacting logic is different between transaction-based tracing and span streaming, the existing crumb tests needed to test both paths, as well as different PII filtering settings.

Additionally:

• Rename span on the aiohttp trace context to _sentry_span

Issues

Reminders

• Please add tests to validate your changes, and lint your code using uv run ruff.
• Add GH Issue ID & Linear ID (if applicable)
• PR title should use conventional commit style (feat:, fix:, ref:, meta:)
• For external contributors: CONTRIBUTING.md, Sentry SDK development docs, Discord community

[sentrivana]

This had to be moved after the PII redaction, because even if we don't want to create a span, we do want to create a breadcrumb, and we need to apply the same PII redacting logic to breadcrumbs.

[sentrivana]

This is just here to make sure we're not creating breadcrumbs the old way in transaction-based tracing anymore. Once all HTTP client integrations have been migrated, the whole function will go away

[github-actions]

Codecov Results 📊

✅ 104314 passed | ⏭️ 6677 skipped | Total: 110991 | Pass Rate: 93.98% | Execution Time: 363m 51s

📊 Comparison with Base Branch

Metric	Change
Total Tests	📈 +330
Passed Tests	📈 +330
Failed Tests	—
Skipped Tests	—

All tests are passing successfully.

✅ Patch coverage is 89.09%. Project has 2478 uncovered lines.
✅ Project coverage is 90.16%. Comparing base (base) to head (head).

Files with missing lines (2)

File	Patch %	Lines
sentry_sdk/integrations/aiohttp.py	86.05%	⚠️ 6 Missing and 4 partials
sentry_sdk/tracing_utils.py	100.00%	⚠️ 1 partials

Coverage diff

@@            Coverage Diff             @@
##          main       #PR       +/-##
==========================================
+ Coverage    90.15%    90.16%    +0.01%
==========================================
  Files          193       193         —
  Lines        25147     25171       +24
  Branches      9136      9146       +10
==========================================
+ Hits         22669     22693       +24
- Misses        2478      2478         —
- Partials      1431      1429        -2

---

Generated by Codecov Action

[ericapisani]

Non-blocking question, otherwise LGTM 🚀

[sentry-warden]

Legacy span path leaks unfiltered URL data into breadcrumbs

In the legacy span else: block, raw parsed_url.query and parsed_url.fragment are added to the breadcrumb unconditionally, bypassing should_send_default_pii/data_collection checks that the streaming path correctly applies.

Evidence

• The streaming span branch (lines 401–447) only adds query/fragment to breadcrumb when has_data_collection_enabled or should_send_default_pii() is true.
• The legacy else: branch at line 460 adds breadcrumb.update(...) inside if parsed_url is not None: with no PII guard at all.
• Since maybe_create_breadcrumbs_from_span previously excluded auto.http.aiohttp, no breadcrumb was ever created for aiohttp; this PR adds breadcrumbs directly in the integration, meaning the unfiltered legacy path now leaks raw query strings to breadcrumbs.
• The PR description explicitly requires breadcrumb data to be subject to PPI filtering, which the legacy path violates.

_{Identified by Warden · find-bugs · ZL9-MZY}