Wraps component destructor in a trycatch

[jima-stripe]

Summary & motivation

When the Payment Element destroys itself, React doesn't always know about it. So when React attempts to unmount the a destroyed PE, an integration error is thrown and the application crashes.

One reproducible scenario of this is when creating a PE with an amount that is too small. The call to elements/session returns an error like this:

No valid payment method types for this configuration. Please ensure that you have activated payment methods compatible with your chosen currency in your dashboard (https://dashboard.stripe.com/settings/payment_methods) and that the `amount` (30) is not lower than the `currency` (usd) minimum: https://stripe.com/docs/currencies#minimum-and-maximum-charge-amounts

Then the loaderror event is triggered. (I believe the component self-destructs in stripe-js, but React still has a reference to it.) So if the merchant attempts to unmount the PE or a wrapper around the PE, the app crashes because it tries to call destroy() on a component that isn't there.

The solution (at least for now)
Wrap the destroy() call in a trycatch, so that it doesn't crash the app.

Testing & documentation

Manually validated the change. Existing tests continue to pass.

[jima-stripe]

FYI @bmathews-stripe and @jackieosborn-stripe

[fruchtose-stripe]

Looks good. I have one point of feedback.

[fruchtose-stripe]