IGNITE-28727 Create internal API method to lock cache entry with specific version

[vldpyatkov]

https://issues.apache.org/jira/browse/IGNITE-28727

[tkalkirill]

A few additional general comments:

1. Please add tests where a lock is acquired via the new API in one transaction and an attempt is made to acquire it via the new API in another; cover both distinct keys and the same key. It would be great to test this with both single-threaded and multi-threaded scenarios.
2. I didn't see a test checking what happens if the new API is called outside of a pessimistic transaction.
3. I didn't see a test checking the behavior regarding lock acquisition after the transaction has completed.
   4.waitTimeoutExpiresFirst should be moved to a shared location so there is only one instance of it, accompanied by a clear comment.

[vldpyatkov]

About the text comment above:

1. Added a test: LockTxEntryOneNodeTest#testLockTxEntryReturnsFalseForLockedKeyAndTrueForOtherKey
2. It is there: LockTxEntryOneNodeTest#testLockTxEntryAsyncFailsInOptimisticTransaction
3. It is here: LockTxEntryOneNodeTest#testLockTxEntryFailsWithoutTransaction
4. Did it.

[github-actions]

Possible compatibility issues. Please, check rolling upgrade cases

This PR modifies protected classes (with Order annotation).
Changes to these classes can break rolling upgrade compatibility.

Affected files:

• modules/core/src/main/java/org/apache/ignite/internal/processors/cache/distributed/near/GridNearLockRequest.java
• modules/core/src/main/java/org/apache/ignite/internal/processors/cache/distributed/near/GridNearLockResponse.java