Refactor redux containers

[Ligerx]

related to #50

Originally I based the redux top level connection from this article https://medium.com/@dan_abramov/smart-and-dumb-components-7ca2f9a7c7d0

Unfortunately it seems that this has not stood the test of time. Hoping to move towards a model where components are responsible for getting their own data. Basically, once a parent component needs to know something about it's child that it doesn't already know, connect the child component up to redux.

Supporting articles
reduxjs/redux#1751 (comment)
https://stackoverflow.com/questions/37264415/how-to-optimize-small-updates-to-props-of-nested-component-in-react-redux/37266130#37266130
https://redux.js.org/faq/react-redux#should-i-only-connect-my-top-component-or-can-i-connect-multiple-components-in-my-tree

If a component that's connected to the store needs to have an ID passed down to it, refer to this pattern
reduxjs/redux#1603

[Ligerx]

If a component that's connected to the store needs to have an ID passed down to it, refer to this pattern
reduxjs/redux#1603

Regarding this statement, if we start using reselect, this could get kind of annoying. Refer to #53