Error boundaries to catch all issues triggered by react

[ddelpiano]

No description provided.

[ddelpiano]

@Robbie1977 this is now implemented in the geppetto-application branch, I am porting shortly in the release_march_2019 branch as well so you can deploy it when you wish.

Quick overview, this now catches all the issue within the VFB render's application, so all the components declared inside VFB will be covered by the ErrorCatcher component.
This has been defined in the ComponentInitialization/Main outside the router in order to cover all the possible scenarios.
At the moment this is the way I implemented, I show a dialog reporting an issue just occurred asking the user if he wants to reload the app or report the issue (through github), the report is actually useful since I am include error message, stack and asking to fill the steps to reproduce the problem.
If you prefer to reload straight that is a small change for me.