[lazerg]

Why: D1, KV, Durable Object storage and SqlStorage calls made outside any active span each became their own root span with no context. They now pass onlyIfParent: true to startSpan, so they only create a span inside an existing trace, like the other db integrations.

How to review: The fix is the onlyIfParent: true option in the five instrumentations. Each test file gets a test that runs one call outside and one inside a parent span and checks that only the one inside creates a span. The existing exact-match assertions needed the new option too.

Unsure about: The SqlStorage fast path (childSpanWillNotBeRecorded) still treats a missing active span as recording, so a query outside a span is sanitized before its span is dropped. I left it as is to keep the change small, happy to move it into the fast path if you prefer.

Closes #25804

[nicohrubec]

after some more internal discussion on the approach for this I'll close this down as superseded by #25879