Create component for surfacing long errors in EuiToasts

[cjcenizal]

As temporarily addressed in #392, toasts can sometimes contain long errors like this:

Toasts are intended to contain very small amounts of content. Because these errors can grow to be very long, it's better to surface them inside a larger container like a modal. It'd be great if we could create a component, e.g. EuiToastError which will present the user with a brief description of the error and a button for seeing the full error. Clicking this button should open the error in a modal with a "Copy to clipboard" button.

[chandlerprall]

Closing this issue. The design team is doing housekeeping against our issues and closing items without much recent activity. Feel free to reopen if you still have issues or feel this is in error.

[cjcenizal]

@chandlerprall This is a very common problem in Kibana. I'm open to tracking it either here or in Kibana, whichever you prefer.

[snide]

It's ok to keep this one open. I know it's a pain point. I've been thinking that maybe Kibana just needs an "error page" that you can go to and get the long form output of any specific error. Think it'd be useful beyond just this toast application (thinking about forms with detailed errors as well). Maybe something we can brainstorm at EAH.

[cchaos]

This is preventing the conversion of Kibana's Notifier to the global toast service. We need to come up with a plan/component/pattern to handle this type of error surfacing.