Fix session factory deserialization with Prevalence Cache

[fredericDelaporte]

Fix #2190

The Bamboo Prevalence cache does serialize entities to disk, with their keys, using binary serialization. NH 5.2 has included the session factory in the serialized data of keys.

This causes a crash when instantiating a session factory using a Prevalence cache having entities serialized, because their deserialization is triggered by the cache provider initialization, which occurs during session factory instantiation, before it registers its name for deserialization resolving. So it cannot deserialize keys due to them failing to deserialize their session factory.

[fredericDelaporte]

This fix, moving name/uuid registration at the beginning of the session factory construction, seems to work and does not cause any old test failure, but is quite debatable.

It allows deserialization to resolve a session factory not yet fully built. And this occurs in this Prevalence cache case, meaning it will recompute its cached entities keys hashcodes with a session factory not yet fully built.

This case is quite wicked. The persisters creation creates the caches, so we have to start their provider before creating the persisters.