Support Role Permissions

-	Identity.Entity now means only Sql Server EF Identity implementation
-	Identity.Entity.InMemory moved to a test project (Identity.Entity.InMemory.Test)
-	Identity.InMemory which was the identity in memory implementation also moved to a test project (Identity.InMemory.Test)
-	IClaimsFactory was promoted to a top level service and now adds any claims found in a Role that a user belongs to.
-	EF implementation now supports logins, claims, roles, two factor, lockouts
-	Initial pass at style cop (mostly line endings since resharper no worky :()
I guess I don't understand that pattern, why would the IdentityBuilder extensions which live in Microsoft.AspNet.Identity show up when you import DI instead of automatically when you import Identity?  That makes sense for ServiceCollection which lives in DI, but not as much for the identity specific builder