Guarantee early actions reach target reducers when app is initializing

[sassanh]

Problem: When app is initializing, one service may dispatch an action and one of its consumers may not be running yet. For example keypad service dispatches the action for setting the mute button state but audio service may not be up yet.

Solutions:

1. Implement a dependency mechanism for services: currently they run in order but there is no guarantee OS prioritizes a thread just cause it ran before another thread. So we can consider adding a mechanism which doesn't run the next thread until the previous thread has registered its reducer. (This is the safest but it will probably make the initialization very slow.)
2. Explicitly make the redux store go into a state in which it only buffers actions and only runs reducer registrations, then again explicitly exit this state and signal redux to dispatch all buffered actions in order.
3. Instead of handling it in redux package, handle it in a middleware in ubo-app.