Use Re-entrant locks instead of synchronized blocks to make driver loom friendly

[mthakur77]

Loom project: https://openjdk.java.net/projects/loom/

Using synchronized keyword pins the virtual thread on the platform thread degrading the performance. Using ReentrantLock should prevent it from happening.

Sample code:

void foo() {
  synchronized(this) {
     ... // performs IO or something blocking
  }
}

With code like:

// loom friendly ...

private final Lock lock = new ReentrantLock();

void foo() {
  lock.lock();
  try {
     ... // performs IO or something blocking
  } finally {
     lock.unlock();
  }
}

[mthakur77]

@mthakur77 please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.

@microsoft-github-policy-service agree [company="{your company}"]

Options:

• (default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.

@microsoft-github-policy-service agree

• (when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.

@microsoft-github-policy-service agree company="Microsoft"

Contributor License Agreement

@microsoft-github-policy-service agree company="Agoda services pvt ltd"

[mthakur77]

raising new one.