[Cascade] Resolve issue that caused "stuttering" in cascade component

[eokoneyo]

Summary

Closes #246949

Previously scrolling through the nested list when its length exceeds the visible viewport, we'd notice an effect after scroll where the rendered items would shift around, this PR fixes this issue.

Context;

This happened because in discover determining the size of the element rendering the content of the nested virtualized list happens by measured the row items, so when content is rendered, given that it is contained in another virtual list that is also measured, the changes in the nested list would in turn cause a measurement to be triggered in the parent, causing the scrolloffset value with which the inner virtualized list was initialised with to be invalid, so the jank we see is the readjustment to the new scrollOffset, what we've opted for is to provide a way to disable propagating these changes to the parent whilst the user is interacting with the nested list.

Visuals

How to test

• Navigate to discover, switch to ES|QL mode
• Make sure to select a large enough time range, so we are returned quite an handful of documents
• Provide the following query FROM kibana_sample_data_ecommerce | STATS count = COUNT(*), PERCENTILE(products.price, 95), AVG(products.tax_amount), SUM(total_quantity) BY products.manufacturer or yours
• Select a row that has quite an extensive number of documents, attempt scrolling through the documents in the row, there should be no jank (aka. stutter).

Checklist

• Unit or functional tests were updated or added to match the most common scenarios

[elasticmachine]

Pinging @elastic/appex-sharedux (Team:SharedUX)

[eokoneyo]

/ci

[eokoneyo]

We opt to count the size of the rows preceding the current row as the scroll margin.

[elasticmachine]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: b5a9601

Failed CI Steps

• FTR Configs #29
• FTR Configs #111
• Scout: [ search / search_homepage ] plugin

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id	before	after	diff
discover	2076	2077	+1

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id	before	after	diff
discover	1.6MB	1.6MB	+873.0B

Public APIs missing exports

Total count of every type that is part of your API that should be exported but is not. This will cause broken links in the API documentation system. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats exports for more detailed information.

id	before	after	diff
@kbn/shared-ux-document-data-cascade	2	3	+1

Unknown metric groups

API count

id	before	after	diff
@kbn/shared-ux-document-data-cascade	28	29	+1

cc @eokoneyo

[Dosant]

code lgtm

[davismcphee]

Works great, thanks for fixing it!

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 251536 locally
cc: @eokoneyo

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 251536 locally
cc: @eokoneyo

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 251536 locally
cc: @eokoneyo

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 251536 locally
cc: @eokoneyo