RFR: 8345266: java/util/concurrent/locks/StampedLock/OOMEInStampedLock.java JTREG_TEST_THREAD_FACTORY=Virtual fails with OOME

[Patricio Chilano Mateo]

Please review this small fix. The call to `Continuation::try_preempt()` can fail and return with a pending OOM exception due to insufficient memory while trying to allocate a new stackChunk. On this particular `OOMEInStampedLock.java` test, the OOM is thrown when returning from Object.wait, which is unexpected and causes the test to fail. But this could also happen when a virtual thread returns from monitorenter, which would cause an assert when coming from compiled code (see `SharedRuntime::monitor_enter_helper()`). Since a failing `try_preempt()` call will just prevent the vthread from being unmounted and force it to follow the normal platform thread code there is no need to throw OOM. The fix is to just clear the pending exception if set, and let future bytecodes handle the OOM condition if still present.

I verified that test `OOMEInStampedLock.java` now passes with the fix. I also added a new more specific test which fails without this fix and passes with it. I also run the change through mach5 tiers1-3.

Thanks,
Patricio

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

Commit messages:
 - v1

Changes: https://git.openjdk.org/jdk/pull/22780/files
  Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=22780&range=00
  Issue: https://bugs.openjdk.org/browse/JDK-8345266
  Stats: 134 lines in 3 files changed: 132 ins; 2 del; 0 mod
  Patch: https://git.openjdk.org/jdk/pull/22780.diff
  Fetch: git fetch https://git.openjdk.org/jdk.git pull/22780/head:pull/22780

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