RFR: 8336299: Improve GCLocker stall diagnostics [v2]

[Neethu Prasad]

> **Notes**
> Adding logs to get more visibility into how fast a thread resumes from allocation stall. 
> 
> **Testing**
> * tier 1, tier 2, hotspot_gc tests.
> 
> Example log messages
> 
> 1. Last thread exiting. Performing GC after exiting critical section. Thread "main" 0 locked.
> 
> 2. Thread exiting critical region Thread "main" 0 locked.
> 
> 3. Thread stalled by JNI critical section. Resumed after 586ms. Thread "Thread-0".
> 
> 4. Thread blocked to enter critical region. Resumed after 1240ms. Thread "SIGINT handler".

Neethu Prasad has updated the pull request incrementally with one additional commit since the last revision:

  Use newer Ticks/Tickspan API and switch to class with scope to hide
  manual call to log_debug_jni

-------------

Changes:
  - all: https://git.openjdk.org/jdk/pull/20277/files
  - new: https://git.openjdk.org/jdk/pull/20277/files/0a245f8e..b2185185

Webrevs:
 - full: https://webrevs.openjdk.org/?repo=jdk&pr=20277&range=01
 - incr: https://webrevs.openjdk.org/?repo=jdk&pr=20277&range=00-01

  Stats: 49 lines in 2 files changed: 30 ins; 18 del; 1 mod
  Patch: https://git.openjdk.org/jdk/pull/20277.diff
  Fetch: git fetch https://git.openjdk.org/jdk.git pull/20277/head:pull/20277

PR: https://git.openjdk.org/jdk/pull/20277