The current deadlock recovery strategy for acquiring OrderedLocks has
the risk of resulting in a StackOverflowError because it performs a
try-and-error recovery in a recursive fashion.
This makes the test method OrderedLockTest.testComplex randomly fail due
to running into a StackOverflowError.

Since the error has primarily been observed when executing the test on
Windows systems, this change temporarily disables the test case on
Windows until a proper improvement of the deadlock recovery has been
merged.