Using react-redux connect deep force update does not work

forceUpdate is ignored by react-redux connect. Because internally a `renderedElement`is stored and forceUpdate does not reset this element, leading to rendering an possibly 'old' component. A fix could be like adding this code to `deepForceUpdate`. Or update react redux connect to handle `forceUpdate`.

```
traverseRenderedChildren(node, internalInstance => {
const instance = internalInstance._instance;
if (instance && instance.renderedElement) {
instance.renderedElement = null;
}
});
```

Start by locating deepForceUpdate and the traversal of rendered children, then inspect how react-redux connect stores renderedElement. Reproduce the forceUpdate case described in the issue and compare the behavior with the proposed reset. Done means connected components no longer render an old element after a deep force update.

Written by the indexing model from the issue text.