Confirm bun-integration-tests need no span streaming port

Part of [SDK-1425](https://linear.app/getsentry/issue/SDK-1425/port-integration-tests-to-span-streaming), one tracking issue per integration test package.

`dev-packages/bun-integration-tests` carries no `traceLifecycle` pin at all, so it already runs on the default streaming lifecycle. `suites/fetch` and `suites/hono-sdk` already assert on streamed spans.

This is a verification issue, not a port. Confirm and close, or split off whatever gap turns up.

## What to check

* No suite pins `traceLifecycle: 'static'` and none uses an env-gated `STREAMED` switch.
* The 5 suites (`basic`, `fetch`, `hono-sdk`, `orchestrion-mysql`, `orchestrion-postgres`) assert on span v2 payloads, not on transaction envelopes. The remaining `transaction:` reference in `suites/hono-sdk/test.ts` is the error event's `transaction` field, which stays.
* The orchestrion suites assert low cardinality `db` span names.

Inspect the five suites under dev-packages/bun-integration-tests: basic, fetch, hono-sdk, orchestrion-mysql, and orchestrion-postgres. Search them for traceLifecycle, STREAMED, transaction envelope assertions, and orchestrion span names, then run the Bun integration tests. Done means the listed checks are confirmed or any discovered gap is split into a follow-up issue.

Written by the indexing model from the issue text.