Sign out should occur in the route after the request is performed.
Additionally, the error from refreshUserData needs to be handled in
route in order to not propagate to parent routes.
If user is logged in and doesn't keep 'recent repositories' tab opened, most of
the pusher events from 'common' channel are useless.
This commit introduces a logic to reject pusher events if:
* recent tab hasn't been opened
* user is signed in
* Travis CI for open source is used
* repository for a given event is not yet in store
* repository for a given event is not part of current user's repositories