removed churn_1m_allGCs

It canbe easily suplied by churn custom. Afaik it is better to remove it
then to disable it

system/churn/README.md

@@ -12,22 +12,19 @@ run.sh can use OTOOL_garbageCollector and OTOOL_JDK_VERSION instead of GC argume
 See https://github.com/rh-openjdk/churn/tree/master/bin for list of supported GCs. The compressed ops in upstream run can be controlled by runner or NOCOMP=-nocoops variable (for run.sh)
 
 ## Running via AQAvit
-
 The support for compressed ops is handled by AQAvit itself. It is currently not sure if churn will be able to honor it. If not, churn will be fixed.
 Similarly the java version and JAVA_HOME are handled by AQAvit.
 
 ### Executing the testsuite
-The `BUILD_LIST of system/churn` contains three targets:
- * _churn_1m_allGCs
+The `BUILD_LIST of system/churn` contains followingtargets:
  * _churn_5h_allGCs
  * _churn_custom
 
 There are major differences in them:
- * churn_1m_allGCs - is testing ground, which runs each GC only for aprox 10 seconds, to simply see if the setup works
  * churn_5h_allGCs - Is running each GC a bit over, which runs each GC for aprox hour and half. A minimum, which can find some real GC issue.
  * churn_custom - this one is to support development, when run on the commandline you need to export at least DURATION and/or OTOOL_garbageCollector (+ many more optional, see [upstream readme](https://github.com/rh-openjdk/churn/blob/master/README)  to select DURATION in seconds and GC(or GCs). So it allows you to test your custom GC - if churn supports that, despite what other churn options suggest (eg `default` or `ALL` thinks).  When running in a Jenkins Grinder job, those are wrapped in CHURN_GCS and CHURN_DURATION
 
-churn_1m_allGCs and churn_5h_allGCs are using pony `ALL` keyword, which is interpreted (based on hardcoded list) as all GC in tested JVM. The set time is divided among them.
+churn_5h_allGCs is using pony `ALL` keyword, which is interpreted (based on hardcoded list) as all GC in tested JVM. The set time is divided among them.
 Note, that if you use `churn_custom` and enumeration, set `CHURN_GCS="ALL"` anyway,  then the time will not be divided. The `CHURN_DURATION` is in seconds. If you use set, off GCs, eg `CHURN_GCS="zgc shenandoah"`, each willt ake the full CHURN_DURATION.
 The `CHURN_GCS="defaultgc"`will set the tested GC to default GC as run.sh think is right. So be aware. Although it is maintained, if your custom JDK have custom GC, it is unlikely to be known. If it have different default gc, it will correctly fail.
 

system/churn/playlist.xml

@@ -13,34 +13,6 @@
 # limitations under the License.
 -->
 <playlist xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="../../TKG/resources/playlist.xsd">
-	<test>
-		<testCaseName>churn_1m_allGCs</testCaseName>
-		<command> 
-            export JREJDK="jdk" ; \
-            export OTOOL_garbageCollector="ALL" ; \
-            export DURATION="60" ; \
-            if [ "x${CHURN_TAP}" == "x" ] ; then  export CHURN_TAP=false  ; fi ; \
-            export TMPRESULTS="$(Q)$(REPORTDIR)$(D)report$(Q)"; \
-            cd $TMPRESULTS ; \
-              bash "$(TEST_ROOT)$(D)system$(D)churn$(D)churn$(D)run.sh"; \
-            $(TEST_STATUS)
-		</command>
-		<levels>
-			<level>dev</level>
-		</levels>
-		<platformRequirementsList>
-			<platformRequirements>os.linux</platformRequirements>
-			<platformRequirements>os.win</platformRequirements>
-			<platformRequirements>os.osx</platformRequirements>
-		</platformRequirementsList>
-		<groups>
-			<group>system</group>
-		</groups>
-		<vendors>
-			<vendor>eclipse</vendor>
-			<vendor>redhat</vendor>
-		</vendors>
-	</test>
 	<test>
 		<testCaseName>churn_5h_allGCs</testCaseName>
 		<command>