RFR: 8373945: vmTestbase eatMemory/ClassUnloader provoke OOME to force GC and might cause GC in other threads [v5]

[SendaoYan]

> Hi all,
> 
> This PR use `WhiteBox.getWhiteBox().fullGC()` instead of `eatMemory` to grigger full GC. The OOME trigger by `eatMemory` may cause vmTestbase/nsk/monitoring/stress/classload tests intermittent fails when run those tests simultancely on some machines. The WB.fullGC() might be use for same purpose. It also reduce test execution time.
> 
> Change has been verified locally by running tests vmTestbase/nsk/monitoring/stress/classload on linux-x64.
> 
> Additional testing:
> 
> - [ ] All jtreg tests by fastdebug build

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

  Increase max iteration for nsk/jvmti/CompiledMethodUnload/compmethunload001/TestDescription.java

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

Changes:
  - all: https://git.openjdk.org/jdk/pull/28891/files
  - new: https://git.openjdk.org/jdk/pull/28891/files/47c508a5..c752a052

Webrevs:
 - full: https://webrevs.openjdk.org/?repo=jdk&pr=28891&range=04
 - incr: https://webrevs.openjdk.org/?repo=jdk&pr=28891&range=03-04

  Stats: 1 line in 1 file changed: 0 ins; 0 del; 1 mod
  Patch: https://git.openjdk.org/jdk/pull/28891.diff
  Fetch: git fetch https://git.openjdk.org/jdk.git pull/28891/head:pull/28891

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