compiler/rtm/locking/ tests have different include/exclude behaviours on different ppc64le machines

Using hotspot_custom target run tests under compiler/rtm/locking/* will get no test selected error on [test-osuosl-ubuntu1804-ppc64le-2](https://ci.adoptopenjdk.net/computer/test-osuosl-ubuntu1804-ppc64le-2) and tests selected either pass or fail on [test-skytap-ubuntu2004-ppc64le-1](https://ci.adoptopenjdk.net/computer/test-skytap-ubuntu2004-ppc64le-1).

Those tests required [@requires vm.rtm.cpu & vm.rtm.compiler](https://github.com/adoptium/jdk19u/blob/master/test/hotspot/jtreg/compiler/rtm/locking/TestRTMAbortRatio.java#L32), which can be set by https://github.com/adoptium/jdk19u/blob/master/test/jtreg-ext/requires/VMProps.java. This different behavior can make jvm_compiler target has different testcases number. Running on [test-osuosl-ubuntu1804-ppc64le-2](https://ci.adoptopenjdk.net/computer/test-osuosl-ubuntu1804-ppc64le-2) testcase is [1073](https://ci.adoptopenjdk.net/job/Grinder/6469/testReport/) and run on [test-skytap-ubuntu2004-ppc64le-1](https://ci.adoptopenjdk.net/computer/test-skytap-ubuntu2004-ppc64le-1) testcase is [1091](https://ci.adoptopenjdk.net/job/Grinder/6476/testReport/). Same with jdk11 https://ci.adoptopenjdk.net/job/Test_openjdk11_hs_extended.openjdk_ppc64le_linux_testList_0/78/testReport/
https://ci.adoptopenjdk.net/job/Test_openjdk11_hs_extended.openjdk_ppc64le_linux_testList_1/86/testReport/
and jdk17:
https://ci.adoptopenjdk.net/job/Test_openjdk17_hs_extended.openjdk_ppc64le_linux_testList_1/81/testReport/
https://ci.adoptopenjdk.net/job/Test_openjdk17_hs_extended.openjdk_ppc64le_linux_testList_1/79/testReport/

This might be a infra issue, need infra's invesitigation.