ISPN-2100 Backport ConcurrentHashMapV8 improvements

* Also made BaseKeyAffinityServiceTest abstract since it's not supposed
to run as a test, and with @AfterTest(alwaysRun=true), the method
appeared to be run on its own.
ISPN-2104 Add methods with java.util.concurrent.TimeUnit for specifying expiration intervals

Overload all methods that take a long millis value to also accept a TimeUnit and perform the conversion to millis internally.
Backward compatibility for users that user Parser, so they could upgrade to newer version without need to change code and recompile
ISPN-2026 Add method for creating cluster with custom global builder
ISPN-2088 Update configuration overrides directly to avoid NPE
ISPN-2111 Disable randomly failing test
ISPN-2058 Tree node move concurrency test broken

Some cleanup:
* Remove some unused imports in tree module
* Remove unused class TreeContext
* Fix some generics related warnings
* Fix a few usages of deprecated cache configuration
* Add NodeAPITest.testGetParent()
ISPN-2058 Tree node move concurrency test broken

* Cache in NodeMoveAPITest must use optimistic locking + write skew check otherwise NodeMoveAPITest.testConcurrency() cannot work
* Rename NodeMoveAPITest to BaseNodeMoveAPITest and add two subclasses that provide appropriate cache configuration for optimistic and pessimistic locking: NodeMoveAPIOptimisticTest and NodeMoveAPIPessimisticTest
* Add BaseNodeMoveAPITest.testConcurrencySimple(), a simpler easier to debug variant of BaseNodeMoveAPITest.testConcurrency()
* Add rollback support via AutoBatchSupport.failAtomic() and use it accordingly in TreeCacheImpl.move(..) to ensure a partial move is never committed and we do not get duplicates
* TreeCacheImpl.move(..) reads the parent node to ensure the write skew check can detect concurrent removals of the child
ISPN-2113 ISPN-2114 Disabling randomly failing tests
ISPN-2095 Use flag to identify atomic map operations

By assigning a flag to all delta writes, such as atomic map writes,
interceptors such as the clustered activation interceptor can decide
more precisely whether to load the previous value or not, which can
be used to merge atomic maps.
ISPN-2105 - KeyAffinityServiceShutdownTest.testSimpleShutdown randomly fails

The KeyAffinityService generator thread only stops after it has filled the queue,
so there is a small interval of time where the queue is full but the thread is
still active.
ISPN-2112 Wait for 10 seconds for views to be installed

* Some of the methods were just waiting for 1 second for the cluster
view to be installed, which in CI environments could be too short.
10 seconds should do fine for all except in individual cases.
ISPN-2110 Avoid unnecessary calls that are no strictly linked with test
some code cleanup and removed user specific stuff from idea settings
ISPN-2106 - StateTransferFunctionalTest.testSTWithThirdWritingNonTxCache and testSTWithThirdWritingTxCache failing randomly

Redesign the serialization to make sure we delay the state transfer and not a random put command.
Wait until the state transfer has ended to check the location of entries.
ISPN-2113 SimpleCacheRecoveryAdminTest.testForceCommitOnOtherNode randomly failing
- the in-doubt transactions are cleared asynchronously  during the lock release phase, so we should wait for the cleanup to finish before asserting that condition
ISPN-2111 ReplicationRetryTest.testPut randomly failing
- I couldn't replicate the failure but fixed a potential race condition and also enhanced the speed of the test by making the connection timeout smaller
ISPN-2085 Don't use batch_mutate for applyModifications as there is now
way to guarantee order of execution on the server
ISPN-2079 ClientConnectionPoolingTest.testMaxActiveReached randomly failing
- the tested condition relied on thread scheduling which is likely the root cause of the intermittent failures. The condition is no longer schedule-dependent now (using a "eventually" call)
ISPN-2108 HeavyLoadConnectionPoolingTest.testHeavyLoad fails randomly
- the assumption wasn't right in the first place as any connection is evictable in 500 millis according to the way the client is configured - it could only pass by chance.  The condition is now fixed and the test was enhanced not to depend on thread scheduling.