test(pyramid): Add span streaming support to integration tests

[ericapisani]

This integration gets span streaming automatically via the SentryWsgiMiddleware and the branching logic in helper methods like set_transaction_name.

Added test coverage to confirm span streaming works as expected.

Fixes PY-2350
Fixes #6048

[linear-code]

PY-2350

[github-actions]

Codecov Results 📊

✅ 282 passed | Total: 282 | Pass Rate: 100% | Execution Time: 43.55s

All tests are passing successfully.

❌ Patch coverage is 60.00%. Project has 14702 uncovered lines.

Files with missing lines (1)

File	Patch %	Lines
pyramid.py	15.04%	⚠️ 96 Missing

---

Generated by Codecov Action

[sentrivana]

Can't comment on the diff since there is none for the main integration file, so just a separate comment:

• _set_transaction_name_and_source technically works as is, but would be nice to use SegmentSource instead of TransactionSource in it when span streaming. There's a streaming SOURCE_FOR_STYLE equivalent in traces.py.
• The integration defines an event_processor; is the data that would be set there set on the span elsewhere (e.g. WSGI), or is there anything we're missing?

[ericapisani]

@sentrivana

_set_transaction_name_and_source technically works as is, but would be nice to use SegmentSource instead of TransactionSource in it when span streaming. There's a streaming SOURCE_FOR_STYLE equivalent in traces.py.

👍🏻

The integration defines an event_processor; is the data that would be set there set on the span elsewhere (e.g. WSGI), or is there anything we're missing?

The event processor adds the parsed request body to the event, so we're technically missing data, but given we had discussed not adding the http.request.body.data span attribute for now on streamed spans, I made no changes there.