DR fails atomicity in 7.3.43

After updating FDB from `7.3.37` to `7.3.43` the disaster-recovery fails atomicity.

What we did:
````
fdbdr start --source /path/to/src.cluster --destination /path/to/dst.cluster
[wait until the DR is a complete copy of the primary database]
fdbdr abort --source /path/to/src.cluster --destination /path/to/dst.cluster
````

Older transactions are fine - but newer transactions are not atomic on the DR-clone.
For example: The secondary-index is there without a primary record.

If I remember correctly this did not happen with `7.3.37`.
Is it safe to downgrade FDB to `7.3.37`? If so, I could check.

Best wishes

Start by reproducing the reported fdbdr start and abort sequence with FoundationDB 7.3.43, after confirming the destination is a complete copy. Compare the resulting DR clone with behavior on 7.3.37, focusing on whether newer transactions preserve primary records and secondary indexes atomically; done means the cause is identified and the regression is covered by a reliable reproduction or test.

Written by the indexing model from the issue text.