Feature/navigator child data tracing

[balazsbajorics]

Before:

After:

Problem:
The data tracing could only start running from a property at an ElementPropertyPath, but in our representation the jsx children are not the same as passing data into props.children, which means the data tracing couldn't trace for data passed in as children to elements.
This limitation meant that #5609 only worked for navigator cartouches that belonged to data passed in as props, not children of elements. You can see in the above before/after screenshots that cartouches representing data coming from useLoaderData are displayed in blue on master.

Fix
#5666 Introduced the ability to start the data tracing from an arbitrary element reference and an ElementPath pointing at their containing scope. This PR uses traceDataFromElement for the navigator data cartouches.

Details:

• The navigator's DataReferenceCartoucheControl takes a new prop surroundingScope and calls traceDataFromElement instead of traceDataFromProp
• Added surroundingScope: ElementPath to DataReferenceNavigatorEntry
• Clarified the code that calls useDataPickerButton in DataReferenceCartoucheControl

[github-actions]

Try me

[relativeci]

#12457 Bundle Size — 62.13MiB (~-0.01%).

0be79db(current) vs 6339ece master#12456(baseline)

Warning

Bundle contains 52 duplicate packages – View duplicate packages

Bundle metrics   2 changes 1 improvement

	Current #12457	Baseline #12456
Initial JS	45.19MiB(~-0.01%)	45.19MiB
Initial CSS	0B	0B
Cache Invalidation	21.31%	0%
Chunks	31	31
Assets	34	34
Modules	4276	4276
Duplicate Modules	509	509
Duplicate Code	31.01%	31.01%
Packages	449	449
Duplicate Packages	52	52

Bundle size by type   2 changes 2 improvements

	Current #12457	Baseline #12456
JS	62.12MiB (~-0.01%)	62.12MiB
HTML	10.94KiB (-0.34%)	10.98KiB

---

Bundle analysis report Branch feature/navigator-child-data-tra... Project dashboard

[github-actions]

Performance test results: