Authentication not completely cleaned-up on logout?

[jordanh]

Issue - Bug

Steps to reproduce:

1. Login as test user (e.g. jordan@parabol.co)
2. Logout using gear menu on dashboard
3. Sign-up as new user
4. Proceed through welcome wizard
5. Observe auth failures on server console

• Estimated effort: 2 points (see CONTRIBUTING.md)

[mattkrick]

This is a symptom of a much larger issue.
Steps required:

• clear cashay cache on logout
• remove socket transport on logout
• use cashay's new @cached for retrieving the user data
• unsubscribe from changefeeds on logout

To unsubscribe, we have a few options:

• unsubscribe from each subscription 1 by 1
• disconnect the socket

The 2nd one sounds best. However, the logout route right now doesn't know about a socket, and I'd like to keep it that way, since being logged in doesn't necessitate a socket (eg welcome wizard, invitation portal).

This is what redux-socket-cluster was kinda built for, but we worked around it by setting the keepAlive to infinity. I've improved it to handle multiple instances of the HOC, so I turned the keepAlive back on.