[Lens][Agg based] Fix table pagination bug for both lens and agg based

[flash1293]

Fixes #139126

There were two problems working together to cause this issue:

• Several places in the code don't check whether a row actually exists before accessing it - this crashes the visualization.
• The Lens table did not reset the page if the data changes to make the current page out of bounds (this worked fine for the agg based table already)

This PR is doing two things:

• Making sure to check whether a row exists before trying access data
• Adding the logic from agg based table to Lens table to reset the page to the last feasible page if the number of rows shrinks due to an update.

The second point can't happen on filter click because the number of rows can shrink due to a large number of different causes (basically everything that triggers a new data load, e.g. hitting refresh, auto-refresh, changing time range, changing the query, ...)

Kapture.2022-08-19.at.11.26.30.mp4

[elasticmachine]

Pinging @elastic/kibana-vis-editors @elastic/kibana-vis-editors-external (Team:VisEditors)

[drewdaemon]

Tested—works great.

[flash1293]

It seems like we are just a few hours too late for 8.4.0, let’s wait until early next week to merge it and release it with 8.4.1

[drewdaemon]

@elasticmachine merge upstream

[kibana-ci]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: b08f64e

Failed CI Steps

• FTR Configs #21

Test Failures

• [job] [logs] FTR Configs #21 / ObservabilityApp Observability alerts / Add to case When user has read permissions for cases does not render case options in the overflow menu

Metrics [docs]

Async chunks

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

id	before	after	diff
lens	1.2MB	1.2MB	+305.0B
visTypeTable	15.7KB	15.9KB	+133.0B
total			+438.0B

History

• 💚 Build #66211 succeeded 2d85f2d
• 💔 Build #66207 failed fd6aada

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

[kibanamachine]

💚 All backports created successfully

Status	Branch	Result
✅	8.4

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation

[kibanamachine]

💔 Some backports could not be created

Status	Branch	Result
❌	8.1	Backport failed because of merge conflicts
✅	8.3

Note: Successful backport PRs will be merged automatically after passing CI.

Manual backport

To create the backport manually run:

node scripts/backport --pr 139160

Questions ?

Please refer to the Backport tool documentation and see the Github Action logs for details