Fix Mutex.tryLock() non-linearizability

[ndkoval]

No description provided.

[qwwdfsad]

Fixes #3745

[qwwdfsad]

Previously, the following interleaving was possible:

tryLock(o)

1. tryAcquire fails
2. holdsLock also fails -- somebody else owns the lock
3. isLocked returned false, yet between 2 and 3 there was a parallel execution that might have locked the mutex with the very same o

[ndkoval]

No, in case "somebody else owns the lock", tryLock() is eligible to return false.

The problem is that:
(0) the mutex was locked with the same owner
(1) tryAcquire() fails
< another thread releases the mutex >
(2) holdsLock(o) fails, as the mutex is unlocked
< another thread acquires the mutex with owner o >
(3) isLocked returns true, and tryLock(o) returns false. However, tryLock(o) should throw an exception.