openjdk: add vmTestbase_nsk_jvmti target

[zzambers]

Adds hotspot vmTestbase_nsk_jvmti target to openjdk tests.
Its part of effort to add VM Testbase tests to aqa.

Testing:
jdk11: RESULTS

• x86-64_linux, aarch64_linux, s390x_linux, x86-64_windows, x86-64_mac: OK

jdk17: RESULTS

• x86-64_linux, x86-64_windows, x86-64_mac: OK

jdk21: RESULTS

• x86-64_linux, aarch64_linux, x86-64_windows, x86-64_mac: OK

jdk25: RESULTS

• x86-64_linux, aarch64_linux, x86-64_mac: OK
• x86-64_windows: 1 FAILURE (rerun OK)
  vmTestbase/nsk/jvmti/ResourceExhausted/resexhausted003/TestDescription.java
• s390x_linux: 1 FAILURE (rerun same)
  vmTestbase/nsk/jvmti/IterateThroughHeap/callbacks/Callbacks.java

[zzambers]

jdk25 / s390x
Failing test:
vmTestbase/nsk/jvmti/IterateThroughHeap/callbacks/Callbacks.java

Output:

----------System.out:(21/2460)----------
[12:19:0.269] Verifying reachable objects.
The following fake exception stacktrace is for failure analysis. 
nsk.share.Fake_Exception_for_RULE_Creation: (Callbacks.cpp:230) Field Lnsk/jvmti/IterateThroughHeap/callbacks/PublicPrimitives;::floatStaticField has unexpected value.
	at nsk_lvcomplain(nsk_tools.cpp:172)
# ERROR: Callbacks.cpp, 230: Field Lnsk/jvmti/IterateThroughHeap/callbacks/PublicPrimitives;::floatStaticField has unexpected value.
# ERROR: Callbacks.cpp, 230: Field Lnsk/jvmti/IterateThroughHeap/callbacks/PublicPrimitives;::floatField has unexpected value.
# ERROR: Callbacks.cpp, 230: Field Lnsk/jvmti/IterateThroughHeap/callbacks/ProtectedPrimitives;::floatStaticField has unexpected value.
# ERROR: Callbacks.cpp, 230: Field Lnsk/jvmti/IterateThroughHeap/callbacks/ProtectedPrimitives;::floatField has unexpected value.
# ERROR: Callbacks.cpp, 230: Field Lnsk/jvmti/IterateThroughHeap/callbacks/PrivatePrimitives;::floatStaticField has unexpected value.
# ERROR: Callbacks.cpp, 230: Field Lnsk/jvmti/IterateThroughHeap/callbacks/PrivatePrimitives;::floatField has unexpected value.
# ERROR: Callbacks.cpp, 230: Field Lnsk/jvmti/IterateThroughHeap/callbacks/DefaultPrimitives;::floatStaticField has unexpected value.
# ERROR: Callbacks.cpp, 230: Field Lnsk/jvmti/IterateThroughHeap/callbacks/DefaultPrimitives;::floatField has unexpected value.
[12:19:0.284] Verifying unreachable objects.
# ERROR: Callbacks.cpp, 230: Field Lnsk/jvmti/IterateThroughHeap/callbacks/PublicPrimitives;::floatStaticField has unexpected value.
# ERROR: Callbacks.cpp, 230: Field Lnsk/jvmti/IterateThroughHeap/callbacks/PublicPrimitives;::floatField has unexpected value.
# ERROR: Callbacks.cpp, 230: Field Lnsk/jvmti/IterateThroughHeap/callbacks/ProtectedPrimitives;::floatStaticField has unexpected value.
# ERROR: Callbacks.cpp, 230: Field Lnsk/jvmti/IterateThroughHeap/callbacks/ProtectedPrimitives;::floatField has unexpected value.
# ERROR: Callbacks.cpp, 230: Field Lnsk/jvmti/IterateThroughHeap/callbacks/PrivatePrimitives;::floatStaticField has unexpected value.
# ERROR: Callbacks.cpp, 230: Field Lnsk/jvmti/IterateThroughHeap/callbacks/PrivatePrimitives;::floatField has unexpected value.
# ERROR: Callbacks.cpp, 230: Field Lnsk/jvmti/IterateThroughHeap/callbacks/DefaultPrimitives;::floatStaticField has unexpected value.
# ERROR: Callbacks.cpp, 230: Field Lnsk/jvmti/IterateThroughHeap/callbacks/DefaultPrimitives;::floatField has unexpected value.
----------System.err:(5/532)----------
WARNING: A restricted method in java.lang.System has been called
WARNING: java.lang.System::loadLibrary has been called by nsk.share.jvmti.DebugeeClass in an unnamed module (file:/home/jenkins/workspace/Grinder/aqa-tests/TKG/output_17778971352434/hotspot_custom_0/work/classes/vmTestbase/nsk/jvmti/IterateThroughHeap/callbacks/Callbacks.d/)
WARNING: Use --enable-native-access=ALL-UNNAMED to avoid a warning for callers in this module
WARNING: Restricted methods will be blocked in a future release unless native access is enabled
...
14:19:00  TEST RESULT: Failed. Execution failed: Execution failed

[zzambers]

jdk 17 and 21 passed on s390x

[jiekang]

Hi @zzambers! For some of the tests in the past we noticed failures on riscv64 and alpine-linux. Can you also expand the scope of your testing for PRs like this to include these platforms?