add universal way for state resolution on server

Nobody has claimed this yet.

Problem on the server is the ability to resolve async actions. On the client it's solved via store middleware, and after the components have actually rendered - actions can be called in the componentDidMount and similar lifeCycle handlers. We need to make sure that all actions that are potentially dispatched by the components are handled

Examples and links of similar solutions:
1. https://github.com/ericclemmons/react-resolver
2. https://github.com/markdalgleish/react-fetcher
3. https://github.com/RickWong/react-transmit (тут relay-like, а не flux-like)
4. https://github.com/erikras/react-redux-universal-hot-example/blob/ca4a8e29eea18bf08148836fed5df359685dbb1b/src/helpers/connectData.js
https://github.com/erikras/react-redux-universal-hot-example/blob/ca4a8e29eea18bf08148836fed5df359685dbb1b/src/helpers/getDataDependencies.js
https://github.com/erikras/react-redux-universal-hot-example/blob/ca4a8e29eea18bf08148836fed5df359685dbb1b/src/redux/middleware/transitionMiddleware.js
5. http://fluxible.io/ - creates abstract app, all state communication goes through "services" and multiple stores, it's possible to call async getContext on the server so that magic happens
6. https://github.com/iam4x/isomorphic-flux-boilerplate/tree/master/shared

Start by reviewing the server-side action-resolution problem described in the issue and comparing the linked react-resolver, react-fetcher, react-transmit, and universal Redux examples. Done means the project has a universal way to resolve async actions potentially dispatched by rendered components on the server, with behavior aligned between server and client.

Written by the indexing model from the issue text.