jdk11_tier1_pack200 is subset of jdk_tools which cause 18 duplicated testcases

**Describe the bug**
A clear and concise description of what the bug is.

jdk11_tier1_pack200 in openjdk/playlist.xml:


jdk_tools in openjdk/playlist.xml:


jdk_tools in TEST.groups:

```
289 jdk_tools = \
290 :core_tools \
291 :svc_tools
```

core_tools in TEST.groups:

```
276 core_tools = \
277 tools \
278 jdk/internal/jrtfs \
279 sun/tools/java \
280 sun/tools/jrunscript
```

duplicated testcases:

```
tools/pack200/AttributeTests.java
tools/pack200/BandIntegrity.java
tools/pack200/DeprecatePack200.java
tools/pack200/InstructionTests.java
tools/pack200/ModuleAttributes.java
tools/pack200/MultiRelease.java
tools/pack200/Pack200Props.java
tools/pack200/Pack200Test.java
tools/pack200/PackageVersionTest.java
tools/pack200/PackChecksum.java
tools/pack200/PackTestZip64.java
tools/pack200/RepackTest.java
tools/pack200/T7007157.java
tools/pack200/TestExceptions.java
tools/pack200/TestNormal.java
tools/pack200/TimeStamp.java
tools/pack200/typeannos/TestTypeAnnotations.java
tools/pack200/UnpackerMemoryTest.java
```

Start with openjdk/playlist.xml and the jdk_tools and jdk11_tier1_pack200 definitions, then read the corresponding jdk_tools and core_tools entries in TEST.groups. Compare the group expansion with the listed tools/pack200 test cases and identify how the overlapping cases should be represented so they run only once.

Written by the indexing model from the issue text.