filter-ed promises not being executed in componentDidMount

`BEGIN_GLOBAL_LOAD`/`END_GLOBAL_LOAD` are dispatched on the client side even when `filter` stops the `asyncConnect` from blocking the render function. However, once the component is mounted, since the redux has saved the state `loaded` as `true`, it does not fetch the data. Due to this you have to manually redo the logic for re-fetching data in these instances. It would be nice to have some logic to ascertain that the promise is executed in `componentDidMount`.

Trace asyncConnect from the filter handling through the client-side BEGIN_GLOBAL_LOAD and END_GLOBAL_LOAD dispatches, then inspect the componentDidMount path and the saved loaded state. Done means filtered promises execute after mounting without requiring manual refetch logic, while the loading behavior remains correct.

Written by the indexing model from the issue text.