Add security context for example PRs using catalog git-clone

The newest versions of the git-clone catalog task don't run as root.
Using this task requires setting the pod's security context to allow writes to volumes
from non-root users.

examples/v1beta1/pipelineruns/pipelinerun-with-final-tasks.yaml

@@ -90,6 +90,9 @@ spec:
   pipelineRef:
     name: clone-cleanup-workspace
   serviceAccountName: 'default'
+  podTemplate:
+    securityContext:
+      fsGroup: 65532 # Make volumes accessible by non-root user for git-clone catalog task
   workspaces:
     - name: git-source
       volumeClaimTemplate:

examples/v1beta1/pipelineruns/pipelinerun.yaml

@@ -245,6 +245,9 @@ spec:
   pipelineRef:
     name: "demo.pipeline"
   serviceAccountName: 'default'
+  podTemplate:
+    securityContext:
+      fsGroup: 65532  # Make volumes accessible by non-root user for git-clone catalog task
   workspaces:
   - name: git-source
     volumeClaimTemplate:

test/yamls/v1beta1/pipelineruns/pipelinerun-with-final-tasks.yaml

@@ -88,6 +88,9 @@ spec:
   pipelineRef:
     name: clone-cleanup-workspace
   serviceAccountName: 'default'
+  podTemplate:
+    securityContext:
+      fsGroup: 65532 # Make volumes accessible by non-root user for git-clone catalog task
   workspaces:
     - name: git-source
       volumeClaimTemplate:

test/yamls/v1beta1/pipelineruns/pipelinerun.yaml

@@ -248,6 +248,9 @@ spec:
   pipelineRef:
     name: demo-pipeline
   serviceAccountName: 'default'
+  podTemplate:
+    securityContext:
+      fsGroup: 65532 # Make volumes accessible by non-root user for git-clone catalog task
   workspaces:
   - name: git-source
     volumeClaimTemplate: