(Split off from JDK-8231032)

After JDK-8229442 many of the vmTestbase tests that use locking are failing because the stacktraces have changed, resulting in unexpected or missing stacktrace elements:

- vmTestbase/nsk/monitoring/ThreadMXBean/ThreadInfo/SynchronizerLockingThreads/SynchronizerLockingThreads*

Checking: nsk.monitoring.share.thread.SynchronizerLockingThreads@6c0bee43
Unexpected stack trace elements for: nsk.monitoring.share.thread.SynchronizerLockingThreads$Thread2@5b76c522
   at java.base@14-ea/java.util.concurrent.ForkJoinPool.managedBlock(ForkJoinPool.java:3137)

- vmTestbase/nsk/monitoring/ThreadMXBean/ThreadInfo/Multi/Multi*

Checking: nsk.monitoring.share.thread.SynchronizerLockingThreads@6d4b092f
Unexpected stack trace elements for: nsk.monitoring.share.thread.SynchronizerLockingThreads$Thread2@766e069
   at java.base@14-ea/java.util.concurrent.ForkJoinPool.managedBlock(ForkJoinPool.java:3137)