Remove the need for base Action Creators to be thunks

[asauber]

Currently, two of our base action creators are thunks, the action creator for updating "ONE" resource and the action creator for updating "MANY" resources.

The reason that these are thunks are to support dynamic accessor properties on the api endpoint configs. Every time a ONE or MANY action is dispatched the dispatch function is passed as part of the action. The reducer then uses this reference to dispatch to attach a thunk with Object.defineProperty ... get on the objects stored in the Redux store. The only reason that these dynamically generated functions are thunks are so they can "cross-cut" the Redux state at runtime.

This is an anti-pattern for multiple reasons. Functions should not be stored in Redux, because Redux stage should be serializable. Also, the Redux store should be as flat as possible, acting as a database for components to aggregate data and map this data to declarative properties.

Refer to this Redux Issue for an extended discussion.
reduxjs/redux#749

This PR removes this pattern, these dynamic properties, and implements flat state access for linode.type and linode.image, which were the only two use cases.

[coveralls]

Coverage increased (+0.1%) to 51.09% when pulling bad2f344a9ef7bf8c4eba5e4c27d8082f118cc18 on asauber:unthunk-action-creators into 3cbb467 on linode:develop.

[rjstires]

Honestly, and with all the sincerity in the world, excellent work. Well on the way to being teachable and testable.

[coveralls]

Coverage increased (+0.06%) to 47.238% when pulling ae2d361 on asauber:unthunk-action-creators into 84827a4 on linode:develop.