RFR: 8347833: CrashOnOutOfMemory should stop GC threads before HeapDumpOnOutOfMemoryError [v2]

[Fairoz Matte]

> When CrashOnOutOfMemory  and HeapDumpOnOutOfMemoryError invoked together, we should make sure, it is performed in a single safepoint, this will avoid allowing other threads to run and throw OOM errors after the initial one is already under error logging.

Fairoz Matte has updated the pull request incrementally with one additional commit since the last revision:

  Aditional work on review comments

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

Changes:
  - all: https://git.openjdk.org/jdk/pull/23519/files
  - new: https://git.openjdk.org/jdk/pull/23519/files/ce22439f..30e95aaa

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

  Stats: 26 lines in 4 files changed: 14 ins; 3 del; 9 mod
  Patch: https://git.openjdk.org/jdk/pull/23519.diff
  Fetch: git fetch https://git.openjdk.org/jdk.git pull/23519/head:pull/23519

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