Fix examples yaml that were not valid

Now that the webhook disallow unknown fields, some examples fails
where they didn't before — which is a good thing.

Signed-off-by: Vincent Demeester <vdemeest@redhat.com>

examples/pipelineruns/clustertask-pipelinerun.yaml

@@ -27,6 +27,4 @@ metadata:
 spec:
   pipelineRef:
     name: sample-pipeline-cluster-task-4
-  trigger:
-    type: manual
   serviceAccount: 'default'

examples/pipelineruns/pipelinerun.yaml

@@ -123,9 +123,9 @@ spec:
       description: Okay this is a hack, but I didn't feel right hard-codeing `-d1` down below
     - name: yamlPathToImage
       description: The path to the image to replace in the yaml manifest (arg to yq)
-    clusters:
-    - name: targetCluster
-      description: Not yet used, kubectl command below should use this cluster
+    #clusters:
+    #- name: targetCluster
+    #  description: Not yet used, kubectl command below should use this cluster
   steps:
   - name: replace-image
     image: mikefarah/yq

examples/taskruns/gcs-resource-spec-taskrun.yaml

@@ -4,10 +4,10 @@ metadata:
   name: list-file
 spec:
   taskSpec:
-   inputs:
-    resources:
-    - name: workspace
-      type: storage
+    inputs:
+      resources:
+      - name: rules
+        type: storage
     steps:
     - name: list
       image: ubuntu

examples/taskruns/git-resource-spec-taskrun.yaml

@@ -5,11 +5,11 @@ metadata:
   name: read-file
 spec:
   taskSpec:
-   inputs:
-    resources:
-    - name: workspace
-      type: git
-      targetPath: skaffold
+    inputs:
+      resources:
+      - name: workspace
+        type: git
+        targetPath: skaffold
     steps:
     - name: read
       image: ubuntu

examples/taskruns/task-multiple-output-image.yaml

@@ -113,8 +113,6 @@ metadata:
 spec:
   taskRef:
     name: multiple-build-push-kaniko
-  trigger:
-    type: manual
   inputs:
     resources:
     - name: sourcerepo