Fix RedisLockRegistryTests for Lock type

The `DistributedLock` type has been introduced in newer version

Author: artembilan

spring-integration-redis/src/test/java/org/springframework/integration/redis/util/RedisLockRegistryTests.java

@@ -1075,13 +1075,13 @@ void sharedDelegateIsDeletedFromRedisOnUnlock() throws Exception {
 
 		// Find two distinct lock keys that share the same ReentrantLock (same DefaultLockRegistry slot)
 		String keyB = null;
-		DistributedLock lockA = null;
-		DistributedLock lockB = null;
+		Lock lockA = null;
+		Lock lockB = null;
 		outer:
 		for (int i = 0; i < 10; i++) {
 			for (int j = i + 1; j < 10; j++) {
-				DistributedLock la = registry1.obtain("key-" + i);
-				DistributedLock lb = registry1.obtain("key-" + j);
+				Lock la = registry1.obtain("key-" + i);
+				Lock lb = registry1.obtain("key-" + j);
 				if (TestUtils.getPropertyValue(la, "localLock") == TestUtils.getPropertyValue(lb, "localLock")) {
 					keyB = "key-" + j;
 					lockA = la;
@@ -1102,7 +1102,7 @@ void sharedDelegateIsDeletedFromRedisOnUnlock() throws Exception {
 		lockB.unlock();
 
 		// Another process must be able to acquire keyB immediately (its Redis key must be deleted)
-		DistributedLock lockBOtherProcess = registry2.obtain(keyB);
+		Lock lockBOtherProcess = registry2.obtain(keyB);
 		assertThat(lockBOtherProcess.tryLock(500, TimeUnit.MILLISECONDS))
 				.as("Redis key for '" + keyB + "' was not deleted on unlock — orphaned lock detected")
 				.isTrue();