Consolidate YAML files [part-8] (#9347)

* Consolidate YAML files [part-8]

This PR exacts the YAML files referenced from the following subdirs:

- docs/concepts/workloads
- docs/concepts/configuration
- docs/concepts/policy

The following problems are fixed:

- docs/concepts/workloads/controllers/ doesnt have a 'cronjob.yaml for
  test
- the exactly same `pod.yaml` was used in both the task/config-pod-container
  topic and the concepts/configuration topics.

* Update examples_test.go

* Add missing yaml file.

content/en/docs/concepts/policy/pod-security-policy.md

@@ -194,7 +194,7 @@ $ alias kubectl-user='kubectl --as=system:serviceaccount:psp-example:fake-user -
 Define the example PodSecurityPolicy object in a file. This is a policy that
 simply prevents the creation of privileged pods.
 
-{{< code file="example-psp.yaml" >}}
+{{< codenew file="policy/example-psp.yaml" >}}
 
 And create it with kubectl:
 
@@ -355,13 +355,13 @@ podsecuritypolicy "example" deleted
 This is the least restricted policy you can create, equivalent to not using the
 pod security policy admission controller:
 
-{{< code file="privileged-psp.yaml" >}}
+{{< codenew file="policy/privileged-psp.yaml" >}}
 
 This is an example of a restrictive policy that requires users to run as an
 unprivileged user, blocks possible escalations to root, and requires use of
 several security mechanisms.
 
-{{< code file="restricted-psp.yaml" >}}
+{{< codenew file="policy/restricted-psp.yaml" >}}
 
 ## Policy Reference
 
@@ -574,4 +574,4 @@ default cannot be changed.
 Controlled via annotations on the PodSecurityPolicy. Refer to the [Sysctl documentation](
 /docs/concepts/cluster-administration/sysctl-cluster/#podsecuritypolicy-annotations).
 
-{{% /capture %}}
+{{% /capture %}}