Summary:
when a transaction reaches lock limit and times out before it attempts to wait for it (9d1a071194/utilities/transactions/lock/point/point_lock_manager.cc (L320)), it can busy-loop forever even though its timeout is expired. This PR fixes this bug by setting a timeout status when its timeout is reached.
This PR also updates the `LockLimit` status from `Busy` to `Aborted`, this matches the check in `Status::IsLockLimit()` and matches the customer usage (c6e4b9f3f9/storage/rocksdb/ha_rocksdb.cc (L10745-L10746)).
Pull Request resolved: https://github.com/facebook/rocksdb/pull/13585
Test Plan: added a unit test that would infinite-loop before this fix.
Reviewed By: jaykorean
Differential Revision: D74077824
Pulled By: cbi42
fbshipit-source-id: 4993d4e4c71bb1594835e9ec6ff4a74d453a9190
0e3e349369