Reduce usage of the user-side session object

[ColdHeat]

The user side session is very difficult to modify. We should only store the user's ID in it.

1. Next major version, cut out all session data besides the user's ID
2. Make a function that takes user ID and returns the user's properties (name, email, role)
3. Cache that function with arguments
4. Invalidate that function's cache key when the user's properties change

[ColdHeat]

All user properties should be relegated to cache items. Banned, verified, etc.

[ColdHeat]

With this approach it might be possible to push sessions back to the user's cookie. Not sure if there would be benefits or not.

[ColdHeat]

This should be closed with 62b5d4f.

The fundamental point to take away is that a user's ID is stored in the session which denotes that they are authenticated. But their actual information should be cached and capable of being invalidated.

Specifically the hash session value can be invalidated to force the user to re-authenticate.