POC: Kibana React Error Boundary

[tsullivan]

Closed: replaced with #169010

Summary

Address #167159

Technical doc [Elastic internal] https://docs.google.com/document/d/1kVD3T08AzLuvRMnFrXzWd6rTQWZDFfjqmOMCoXRI-14/edit

This PR creates the KibanaErrorBoundary component and KibanaErrorService utility, and shows it in use in two main areas that control lazy-loaded UI elements:

1. Stack Management. This PR handles the error that could occur when navigating across management apps, and async code needed to render the app failed to load.
   

2. Share Menu Manager. This PR handles the error that could occur when the Share Menu Manager calls on a ShareMenuItem to render itself, and async code that is needed fails to load.

Testing

1. Use a script proxy in between the browser and the Kibana server. Try https://github.com/tsullivan/simple-node-proxy
2. Script the proxy to send 404 responses for the Reporting plugin bundle, and for a bundle of some Management app.
3. Try the Share > CSV menu in Discover. It should be blocked, and handled with a toast message. Buttons in the toast should work.
4. Try the management app. It should be blocked, and handled with an EuiCallout. Refresh button and EuiAccordion should work.

Checklist

Delete any items that are not applicable to this PR.

• Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
• Documentation was added for features that require explanation or tutorials
• Unit or functional tests were updated or added to match the most common scenarios
• Any UI touched in this PR is usable by keyboard only (learn more about keyboard accessibility)
• Any UI touched in this PR does not create any new axe failures (run axe in browser: FF, Chrome)
• If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the docker list
• This renders correctly on smaller devices using a responsive layout. (You can test this in your browser)
• This was checked for cross-browser compatibility

[tsullivan]

The first PR will not implement the "inline" error treatment, but only the "callout" treatment.

I'm keeping this as a closed PR so we can come back and reference the full POC implementation.

Replacing this PR with #168754

[kibana-ci]

💔 Build Failed

• Buildkite Build
• Commit: 6371301
• Interpreting CI Failures
• Storybooks Preview

Failed CI Steps

• Build API Docs
• Jest Tests #17
• Osquery Cypress Tests #5
• Security Solution Cypress tests, burning changed specs #1
• Check Types

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id	before	after	diff
core	486	491	+5
share	72	77	+5
total			+10

Async chunks

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

id	before	after	diff
share	5.5KB	5.0KB	-490.0B

Page load bundle

Size of the bundles that are downloaded on every page load. Target size is below 100kb

id	before	after	diff
core	366.3KB	367.3KB	+994.0B
share	52.0KB	56.2KB	+4.2KB
total			+5.2KB

History

• 💛 Build #167536 was flaky 642c396
• 💔 Build #167176 failed 8a00c07d86b612bd19f88bb540fefec065ee23e7
• 💔 Build #166851 failed c4eacc250e4e0913df14c3f0ee6ad658650cda9c
• 💔 Build #166850 failed d713a9cbfc6daa46a7f7da4af6f91e94e6b81d0f

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