composite-checkout: Add error boundary around top level (1)

[sirbrillig]

Changes proposed in this Pull Request

This adds a React error boundary around the entire component tree of composite checkout starting at CheckoutSystemDecider. Hopefully this will never be hit because composite checkout already has several layers of error boundaries within CheckoutProvider but it will give us the opportunity to:

1. Prevent the user from seeing a blank screen if something at the top level fails.
2. Record such errors and report them to logstash where they will ping us in Slack.

Testing instructions

• Trigger a fatal error inside the CompositeCheckout component itself.
• Verify that the logstash logs for the string composite checkout load error get a new entry.

[matticbot]

Test live: https://calypso.live/?branch=add/checkout-error-boundary-at-system-decider

[matticbot]

Here is how your PR affects size of JS and CSS bundles shipped to the user's browser:

Sections (~83 bytes added 📈 [gzipped])

name      parsed_size           gzip_size
checkout       +391 B  (+0.0%)      +83 B  (+0.0%)

Sections contain code specific for a given set of routes. Is downloaded and parsed only when a particular route is navigated to.

Legend

What is parsed and gzip size?

Parsed Size: Uncompressed size of the JS and CSS files. This much code needs to be parsed and stored in memory.
Gzip Size: Compressed size of the JS and CSS files. This much data needs to be downloaded over network.

Generated by performance advisor bot at iscalypsofastyet.com.

[michaeldcain]

With the import fixed, this works as expected. The correct message appears on both the page and in the logs. Let's watch the logs after this merges, it might be nice to make the message more helpful for the user if we see a number of these.

[sirbrillig]

Thanks! I clearly didn't have time to test this last night.

[michaeldcain]

Tested, works as described. LGTM.

[a8ci18n]

This Pull Request is now available for translation here: https://translate.wordpress.com/deliverables/3848930

Hi @sirbrillig, could you please edit the description of this PR and add a screenshot for our translators? Ideally it'd include this string: Sorry, there was an error loading this page.

Thank you in advance!

[a8ci18n]

Translation for this Pull Request has now been finished.