fixup! Recompute hashcodes on deserialization

Additional cleanup

Author: fredericDelaporte

src/NHibernate/Cache/FilterKey.cs

@@ -50,7 +50,6 @@ public override int GetHashCode()
 		{
 			var result = 13;
 			result = 37 * result + _filterName.GetHashCode();
-
 			result = 37 * result + CollectionHelper.GetHashCode(_filterParameters, NamedParameterComparer.Instance);
 			return result;
 		}

src/NHibernate/Engine/EntityKey.cs

@@ -110,14 +110,5 @@ public override string ToString()
 		{
 			return "EntityKey" + MessageHelper.InfoString(factory.GetEntityPersister(EntityName), Identifier, factory);
 		}
-
-		/// <summary>
-		/// To use in deserialization callback
-		/// </summary>
-		/// <param name="sessionFactory"></param>
-		internal void SetSessionFactory(ISessionFactoryImplementor sessionFactory)
-		{
-			factory = sessionFactory;
-		}
 	}
 }

src/NHibernate/LockMode.cs

@@ -121,10 +121,6 @@ public bool Equals(LockMode other)
 
 		public override int GetHashCode()
 		{
-			// If the object is put in a set or dictionary during deserialization, the hashcode will not yet be
-			// computed. Compute the hashcode on the fly. So long as this happens only during deserialization, there
-			// will be no thread safety issues. For the hashcode to be always defined after deserialization, the
-			// deserialization callback is used.
 			unchecked
 			{
 				return (level * 37) ^ (name?.GetHashCode() ?? 0);