jdk_svc_sanity and jdk_jfr has duplicate subset testcases jdk_jfr_sanity

jdk_svc_sanity = \
:jdk_management_sanity \
:jdk_instrument_sanity \
:jdk_jmx_sanity \
:jdk_jdi_sanity \
:jdk_jfr_sanity \
:svc_tools_sanity

jdk_jfr = \
jdk/jfr

jdk_jfr_sanity = \
jdk/jfr/api/recording/event/TestLoadEventAfterStart.java \
jdk/jfr/api/recording/state/TestState.java \
jdk/jfr/event/os/TestCPULoad.java \
jdk/jfr/event/compiler/TestAllocInNewTLAB.java \
jdk/jfr/jcmd/TestJcmdStartStopDefault.java \
jdk/jfr/event/io/TestFileStreamEvents.java \
jdk/jfr/event/compiler/TestCompilerCompile.java \
jdk/jfr/event/gc/collection/TestGCGarbageCollectionEvent.java \
jdk/jfr/event/runtime/TestClassLoadEvent.java \
jdk/jfr/event/runtime/TestJavaBlockedEvent.java \
jdk/jfr/event/gc/collection/TestGCWithFasttime.java \
jdk/jfr/event/gc/configuration/TestGCConfigurationEvent.java

Twelve testcases are duplicate

Start by locating the definitions of jdk_svc_sanity, jdk_jfr, and jdk_jfr_sanity in the test configuration, then compare the twelve listed JFR testcases with the suite composition. Verify how subset suites are expanded and confirm that the completed definitions no longer schedule those cases twice.

Written by the indexing model from the issue text.