[Bug]: Datom input order is generally not registered within a transaction causing complicated upserts

[jsmassa]

What version of Datahike are you using?

0.5.1501

What version of Java are you using?

11.0.13 2021-10-19

What operating system are you using?

Ubuntu

What database EDN configuration are you using?

{:index :datahike.index/persistent-set}

Describe the bug

The test in datahike.test.upsert-impl-test/temporal-upsert fails for the persistent set due to the unknown insert order of datoms when they occur in the same transaction.

This is probably the cause for the op-count entry introduced in the hitchhiker-tree operations, but this solution is not optimal since it will cause the problem to occur with each new index data structure. A better solution would be to produce the (temporal) datoms to be added/retracted for the entire transaction entity as a batch and then apply the operations.

What is the expected behaviour?

Same as for the hitchhiker-tree.

How can the behaviour be reproduced?

Replace the index used in this test with the persistent-set index.