Initial IDistributedCache abstraction and implementations.

This includes:
- The IDistributedCache abstraction
- An implementation using MemoryCache
- An implementation using Redis.

This does not include
- Any serialization helpers
- Any concurrency controls (optimistic, locking, etc.).

Notes:
- Resis does not have any notion of sliding expiration, only absolute expiration. It does allow a single entry to contain multiple key-value pairs of data. We use this to store the absolute and sliding expiration values with the data and retrieve them later when we want to re-calculate the expiration.
- Some redis operations are best implemented via LUA script sent to the server. I've done the critical ones that way so far, but there are a few more (like refresh) that could be optimized via script.
This certainly sounds like it's worth logging a bug on. The bug ought to cover the general problem of when to open a connection, plus a separate dependent bug on fixing up the tests to not always open a connection.

Regarding opening a connection on demand, I believe that's what EF does, and I'm not sure it's that big a problem... but worth discussing.