Split out EntityOwnershipService implementation from distributed-datastore

We are currently fusing the two concepts – the datastore and the EOS implementation. This hurts readability in that it is difficult to discern which components are part of what.

Separate out EOS implementation into a separate artifact, so that the two can evolve independently – notably the EOS implementation should be able to operate purely on sal-akka-raft.