ISPN-2985 Allow passing in a pre-built SSLContext to the HotRod server and client (for Server usage)
ISPN-3040 Fix parent POM schema compatibility by placing combine.self on the appropriate elements
Move some needlessly verbose logging from debug to trace and fix misspelling
Add a bit of logging and replace viewId with topologyId
RehashAfterJoinWithPreloadTest cleanup
State transfer code cleanup

* Rename StateTransferManager.notifyEndOfTopologyUpdate() to notifyEndOfRebalance() to reflect its actual purpose
* Remove unused method StateTransferManager.isLocalNodeFirst()
* Clarify javadoc LoLocalTopologyManager.confirmRebalance()
ISPN-2589 NPE in InvalidateL1Command

This NPE can appear in both DIST and REPL mode when we process a topology update in which the current node is not a member.

* There is no reason to invalidate segments if we are not a member, so the call to StateConsumerImpl.invalidateSegments() is guarded with a membership check. This also avoids the NPE.
* StateConsumerImpl.invalidateSegments() was wrongly using CommandsFactory.buildInvalidateFromL1Command where it should actually be buildInvalidateCommand()
* Extract all the logic to restart broken transfers from failed sources into a separate method (StateConsumerImpl.restartBrokenTransfers())
* Rename StateConsumerImpl.notifyEndOfTopologyUpdate() to notifyEndOfRebalanceIfNeeded() to clarify its purpose
* Remove StateConsumerImpl.activeTopologyUpdates member as all the logic regarding it has long become redundant
* Remove one of the overloaded variants of CommandsFactory.buildInvalidateFromL1Command that is no longer used
ISPN-2173 NPE when using XA enlistment without recovery

If recovery is not enabled the call to TransactionXaAdapter.forget() must be no-op instead of failing due to NPE.
ISPN-2549 Invalidation mode caches with pessimistic transactions may result in stale remote locks

* In transactional mode InvalidationInterceptor.invalidateAcrossCluster() should not just send a bare InvalidateCommand to the other nodes. The invalidate command should be wrapped in a PrepareCommand so it executes in a transaction and locks can be acquired and release appropriately.

* EntryWrappingVisitor must also visit InvalidateCommands. This was not needed until now because invalidation was never executed in tx.