Add pagination control to datavisualizer failures to rendering all errors at a single time

[nreese]

To view problem:

1. use ML data visualizer to import a file with lots of errors. For example, download https://alaska.usgs.gov/data/wildlifeTracking/bird/loon/yellowBilledLoon/argos/yellowBilledLoon_USGS_ASC_argos_processedData.zip from https://www.usgs.gov/centers/asc/science/tracking-data-yellow-billed-loons-gavia-adamsii?qt-science_center_objects=0#qt-science_center_objects. Unzip the file and import "processedData/yellowBilledLoon_USGS_ASC_argos_diag_filteredLocations.csv".
2. everything runs fine until the import is finished and the results are rendered. Then the browser tries to render all 149066 failures and fails over.

This PR fixes the problem by adding a pagination control to failures so a reasonable amount of failures are rendered at a time.

[elasticmachine]

Pinging @elastic/ml-ui (:ml)

[nreese]

@elasticmachine merge upstream

[jgowdyelastic]

LGTM

[nreese]

@elasticmachine merge upstream

[kibanamachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: e0b7a22
• Storybooks Preview

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id	before	after	diff
ml	1741	1742	+1

Async chunks

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

id	before	after	diff
ml	6.4MB	6.4MB	+930.0B

History

• 💚 Build #111701 succeeded a4c9ef4
• 💚 Build #111524 succeeded b73b2a0
• 💔 Build #111521 failed 478cb9c

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