Make sure the app never white screens by adding a top level error boundary. Right now we only have error boundaries for details and list pages and a few other specific places. While we hope to not have runtime errors, a white screen is not a good user experience and doesn't give the user any details to use when reporting a bug.

We should be able to reuse our existing error boundary component:

https://github.com/openshift/console/blob/master/frontend/packages/console-shared/src/components/error/error-boundary.tsx

Let's look at refactoring this to be a functional component with hooks instead of a class component as part of this story.

To test this, we might need to mock an API request to return bad data to trigger a runtime error in console.

https://docs.cypress.io/api/commands/intercept/

Acceptance Criteria

1. Error boundary is added to the entire app so that it never shows a blank page
2. The error boundary component is updated to be a functional component
3. We have tests in CI to make sure the error boundary is working. Tests should also exercise the error boundaries on list and details pages.

Non Goals

This story does not cover adding error boundaries for plugins, which will be handled as part of the dynamic plugin epic.