Refactor NeoStoreDataSource

Refactors NeoStoreDataSource into modules, and introduces Recovery,LogRotation, and LogPruning as separate processes.

The recovery process now works on its own channel to the underlying logs, so there is no longer any assumption that after recovery PhysicalLogicalLog can continue with the same channel. Instead it opens its own channel and moves to the end.

UpdateableSchemaState and its implementation didn't have anything to do with IAGD, so it was moved into NSDS.

Log pruning is now a separate process, that uses monitor callbacks to trigger when to run.
So this class is `Monitor` which executes pruning logic after `rotatedLog` event.
Is this monitor-controlled-flow a good thing? I thought monitors should only be used for stats gathering, logging etc.