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 :()
Thinking about it more, these constructors on the base DbContext type are not necessarily there for DI. There is probably always going to be one that takes DbContextOptions directly on DbContext for usage in direct user code. The question is, should we have that on IdentityContext?