Exclude problematic testcases from AIX platform

[smlambert]

Follow-up for what is seen during Jan release, related (#4983 (comment))

• exclude renaissance-philosophers for AIX
  • check on jck-skytap-aix72-ppc64-4 as per note below, in the event some machines have enough memory to support this test, and query whether all machines could have similar configuration
• jdk_tools ->JliLaunchTest.sh as non-blocking, to be excluded and Bad address issue to be investigated after the release period
• mark jdk_jdi -> com/sun/jdi/ThreadMemoryLeakTest.java as non-blocking, to be excluded and investigated post-release.
  • @sxa noted that he was able to get this to pass on a particular machine (SXA: Assuming my invocation was correct and valid, I've managed to get this to pass from the command line on jck-skytap-aix72-ppc64-4) - before exclusion, rerun in Grinder with multi ITERATIONS to determine if intermittent and/or different behaviour on different machines

[sophia-guo]

Recheck com/sun/jdi/ThreadMemoryLeakTest.java status.
Grinder https://ci.adoptium.net/view/Test_grinder/job/Grinder/9196/
JliLaunchTest.sh. --> JliLaunchTest.java

[smlambert]

See JDK22 dry run triage here:
#5141 (comment)
where ThreadMemoryLeakTest and JliLaunchTest both fail.