Display 'Prediction Result' as a separate component

[jeff1evesque]

Instead of rendering the Prediction Result as a separate fieldset, at the bottom of the webpage:

We should display it as a separate component, on it's own dedicated webpage. Additionally, we'll need to allocate the new webpage, it's own dedicated route definition. Therefore, the /session/model-predict page will need to provide a <Link> to the new result page, upon prediction completion. To make all this work, we'll need to store the results into redux, so it can be accessible within the new prediction result page.

[jeff1evesque]

55b26a7: probably should have gone into it's own dedicated issue. However, we decided to simplify, and standardize all reactjs filenames, and corresponding classnames.

[jeff1evesque]

When we click the above Goto results button, we are correctly redirected:

However, we need to debug whether our redux is not properly wired, or our results page logic doesn't properly decouple the results object, into presentational content. In the future, we may consider storing our results into sessionStorage, since on a browser refresh our redux store will be emptied.

[jeff1evesque]

We are able to discern that our presentational content is available, as indicated in the console.log output:

However, we have not properly decoupled the data from our corresponding redux container.

[jeff1evesque]

We are receiving Warning: Each child in an array or iterator should have a unique "key" prop.:

[jeff1evesque]

We are receiving SCRIPT438: Object doesn't support property or method 'entries' within Internet Explorer, after clicking the Goto results button: