docs(scopes): Add image for scope inheritance/merging (#15259)

## DESCRIBE YOUR PR


This image already exists on the "Hub & Scope Refactoring" page, but is
now also added to the "Scopes" page to make the content easier to grasp.


## IS YOUR CHANGE URGENT?  

Help us prioritize incoming PRs by letting us know when the change needs
to go live.
- [ ] Urgent deadline (GA date, etc.): <!-- ENTER DATE HERE -->
- [ ] Other deadline: <!-- ENTER DATE HERE -->
- [ ] None: Not urgent, can wait up to 1 week+

## SLA

- Teamwork makes the dream work, so please add a reviewer to your PRs.
- Please give the docs team up to 1 week to review your PR unless you've
added an urgent due date to it.
Thanks in advance for your help!

## PRE-MERGE CHECKLIST

*Make sure you've checked the following before merging your changes:*

- [ ] Checked Vercel preview for correctness, including links
- [ ] PR was reviewed and approved by any necessary SMEs (subject matter
experts)
- [ ] PR was reviewed and approved by a member of the [Sentry docs
team](https://github.com/orgs/getsentry/teams/docs)

Author: s1gr1d

develop-docs/sdk/telemetry/scope-inheritance.png

@@ -49,6 +49,8 @@ Data from all three scope types MUST be merged in a specific order before being
 3. merged with data from the current scope, which is ...
 4. applied to the event
 
+![Scope Inheritance](scope-inheritance.png)
+
 ## Related Documents
 
 This document provides a concise summary of the [Hub & Scope Refactoring](/sdk/miscellaneous/hub_and_scope_refactoring/), focusing on implementation details and expected features. The original document remains unchanged, offering additional historical context and migration strategies.