docs(scopes): Add graphics for scope forking (#11702)

Author: s1gr1d

develop-docs/sdk/miscellaneous/hub_and_scope_refactoring.mdx

@@ -166,6 +166,12 @@ This image illustrates the behavior of these new APIs and how scope data is appl
 
 For a zoomable version visit the <a href="https://miro.com/app/board/uXjVNtPiOfI=/?share_link_id=140058397661" target="_blank">Miro Board</a>
 
+The below image is a simplified overview of how the scope forking/inheritance works.
+The last item on the timeline shows that there can be multiple active scopes on one server, but they don't share data (except for the global scope).
+Each new request and each new user gets its own, new isolation scope.
+
+![Scope Inheritance](scope-inheritance.png)
+
 Here's how the new APIs roughly map to the old-style APIs. In case of `configure_scope` and `push_scope` it's not clear-cut whether to use the current or the isolation scope. The choice essentially depends on how long/for which context the changed/forked scope should be active.
 
 <table>