fix(rust): implement abort commit for S3DynamoDBLogStore

[PeterKeDer]

Description

This PR ensures when using S3DynamoDBLogStore, temp commit files are only deleted when the DynamoDB log entry is deleted.

Add abort_commit_entry(version, tmp_commit) to LogStore

• By default, this just deletes the tmp_commit file
• For S3DynamoDBLogStore, it first deletes the DynamoDB entry. Then, it only deletes tmp_commit if the entry is deleted successfully

Context

This fixes a rare bug when using DynamoDB as the locking provider. Consider the following events:

1. S3DynamoDbLogStore.write_commit_entry succeeds at creating a DynamoDB entry, but fails during repair_entry
2. The error handling deletes the tmp_commit file
3. The next time repair_entry is called on this entry, it will lead to ObjectStoreError::NotFound since the temp commit file was deleted
4. We infer the temp commit json was already moved, so we update the DynamoDB entry as complete

This results in a complete DynamoDB log entry, even though the corresponding transaction log does not exist in _delta_log.

Related Issue(s)

• fix(rust): do not delete the temp commit file when write_commit_entry returns error #2446