🐃 Ordering tie breaker can cause undefined ordering with the same identity

[DanielVF]

The current log ordering uses the Lamport clock first, then breaks ties by using the public id of the Orbit DB identity that created the entry.

Because of the current limitation on changing access controls after a database is created, it's often required for a single identity to be reused by the same user on different devices. This means however that the same identity may by syncing with itself. In this case there may be entries with identical clock .id and clock.time fields. This can cause ordering to become non-deterministic.