vmTestbase/vm/mlvm/hiddenloader/stress/oome/metaspace/Test.java passes only when run locally JDK17 arm linux

From the JDK17 April 2026 dry run triage https://github.com/adoptium/aqa-tests/issues/7009#issuecomment-4260086340

Failure on JDK17 arm linux: vmTestbase/vm/mlvm/hiddenloader/stress/oome/metaspace/Test.java passes only when run locally, passed on test-docker-ubuntu2404-armv7-10

Hits an OOME failure when run in jenkins,
```
[16:4:25.55] ### TRACE 1: Test started.
[16:4:25.98] ### TRACE 1: RNG seed = 8889428613154436483 (0x7b5d9839b7437583)
For random generator using seed: 8889428613154436483
To re-run test with same seed value please add "-Djdk.test.lib.random.seed=8889428613154436483" to command line.
[16:4:28.365] ### TRACE 1: Caught OOME : Java heap space
[16:4:28.377] # ERROR: Test caught an exception:
[16:4:28.377] # ERROR: java.lang.RuntimeException: TEST FAIL : wrong OOME
[16:4:28.378] # ERROR: at vm.mlvm.hiddenloader.stress.oome.metaspace.Test.checkOOME(Test.java:66)
[16:4:28.378] # ERROR: at vm.mlvm.share.MlvmOOMTest.run(MlvmOOMTest.java:53)
```
When run locally it uses these options
```
-XX:MaxRAMPercentage=25 -XX:-UseGCOverheadLimit -XX:MetaspaceSize=10m -XX:MaxMetaspaceSize=20m
```
So I think one or more of these options are being overridden when run in a jenkins environment. Bear in mind this arm linux environment runs in a docker container

Start with vmTestbase/vm/mlvm/hiddenloader/stress/oome/metaspace/Test.java and the failure path at Test.java:66, then read vmTestbase/vm/mlvm/share/MlvmOOMTest.java. Re-run with the reported random seed and compare the local and Jenkins Docker JVM options, especially the memory settings. Done means identifying why Jenkins reports Java heap space instead of the expected metaspace OOME and making the test pass reliably in that environment.

Written by the indexing model from the issue text.