Resolve lock bug

[Surrina-ki]

7d80f59#diff-3ac08ac53a85faf27689aba58b5ba02e85714d1d4e325835d018a76d48c60bf1
In this commit, the logic related to lock resolution was modified, but I've found that the current implementation is still not comprehensive enough. For example, with async commit, if only prewrite is executed and the secondary commits are never performed, subsequent reads of the written data will keep failing with "Failed to resolve lock".

[ti-chi-bot]

Welcome @Surrina-ki! It looks like this is your first issue to tikv/client-rust 🎉

[Surrina-ki]

Currently, when checking the transaction status and encountering a lock, nothing is executed. However, I noticed that in client-go, when a lock is encountered and it belongs to an async commit transaction, the client does send requests such as CheckSecondaryLocksRequest and ResolveLockRequest to attempt to resolve the lock. Could you please take a look? @pingyu

[pingyu]

Async commit is not implemented yet. Please refer to description of #519:

Resolving pessimistic & async commit locks is not implemented yet.

[Surrina-ki]

Async commit is not implemented yet. Please refer to description of #519:

Resolving pessimistic & async commit locks is not implemented yet.

Is there a planned timeline for implementing async commit lock support?