Switch back to getting populated user objects in Twitter responses.
Switch back to getting populated user objects in Twitter responses.

Having to fetch users separately was causing more HTTP requests and memcache
operations, increasing costs. Now that Twitter Digest supports If-Modified-Since
and edge caching, it should need to re-parse cached JSON data less often, so the
heavier responses represent less overhead (see
https://github.com/mihaip/streamspigot/commit/6abf3b8721e62ce7aa900e6878e72f746a05ec56
for original rationale for this change).

mihaip/streamspigot,mihaip/streamspigot,mihaip/streamspigot,mihaip/streamspigot