ref(span-first): Clarify application of scope data to spans (#15773)

Clarifies which spans get which data from the scopes:
- scope attributes are applied to all spans
- scope contexts and request data is only applied to segment span

Author: Lms24

develop-docs/sdk/telemetry/spans/implementation.mdx

@@ -76,10 +76,11 @@ Here's a rough overview of what `captureSpan` should do in which order:
 1. Accept any span that already ended (i.e. has an `end_timestamp`)
 2. Obtain the current, isolation and global scopes and merge the scope data.
 3. Apply [common span attributes](../span-protocol/#common-attribute-keys) from the client and the merged scope data to every span.
-4. Apply the merged scope data (including scope attributes) to the span IFF it is a segment span.
-5. Apply any span processing hooks (i.e. event processor replacements) to the span.
-6. Apply the `before_send_span` callback to the span.
-7. Enqueue the span into the span buffer.
+4. Apply [scope attributes](../../scopes/#setting-attributes) from the merged scope data to every span.
+5. Apply `contexts` and `request` data from the merged scopes to the segment span only.
+6. Apply any span processing hooks (i.e. event processor replacements) to the span.
+7. Apply the `before_send_span` callback to the span.
+8. Enqueue the span into the span buffer.
 
 The `captureSpan` pipeline MUST NOT 
 - drop any span