Update scc to add seccompProfiles to handle restricted securityContext

Context:

As part of addressing https://issues.redhat.com/browse/OCPSTRAT-487, there's a plan to enable restricted security context by default starting from Openshift 4.16.
Once this becomes the default setting, existing Triggers functionality may break.
This is because we currently set security context to false, and the pipelines-scc security context constraint (SCC)
doesn't have seccompProfiles: runtime/default, which is required when restricted security context is enabled by default.

cmd/openshift/operator/kodata/openshift/00-prereconcile/openshift-pipelines-scc.yaml

@@ -32,6 +32,8 @@ seLinuxContext:
   type: MustRunAs
 supplementalGroups:
   type: RunAsAny
+seccompProfiles:
+- runtime/default
 volumes:
 - configMap
 - downwardAPI

pkg/reconciler/openshift/tektontrigger/extension.go

@@ -36,7 +36,6 @@ func (oe openshiftExtension) Transformers(comp v1alpha1.TektonComponent) []mf.Tr
 		occommon.RemoveRunAsUser(),
 		occommon.RemoveRunAsGroup(),
 		occommon.ApplyCABundles,
-		replaceDeploymentArgs("-el-security-context", "false"),
 		replaceDeploymentArgs("-el-events", "enable"),
 	}
 }