docs: Remove references to pemCertificate and pemPrivateKey functions (#3744)

* Update docs

Fixes #3260 Removes old deprecated template function 

Signed-off-by: Tyler Renslow <tdrenslow@gmail.com>

* Update templating-v1.md

Signed-off-by: Tyler Renslow <tdrenslow@gmail.com>

---------

Signed-off-by: Tyler Renslow <tdrenslow@gmail.com>

docs/guides/templating-v1.md

@@ -18,7 +18,7 @@ You can use templates to inject your secrets into a configuration file that you
 
 You can also use pre-defined functions to extract data from your secrets. Here: extract key/cert from a pkcs12 archive and store it as PEM.
 ``` yaml
-{% include 'pkcs12-template-v1-external-secret.yaml' %}
+{% include 'pkcs12-template-v2-external-secret.yaml' %}
 ```
 
 ### TemplateFrom

docs/snippets/gcpsm-tls-externalsecret.yaml

@@ -14,8 +14,8 @@ spec:
     template:
       type: kubernetes.io/tls
       data:
-        tls.crt: "{{ .mysecret | pkcs12cert | pemCertificate }}"
-        tls.key: "{{ .mysecret | pkcs12key | pemPrivateKey }}"
+        tls.crt: "{{ .mysecret | pkcs12cert }}"
+        tls.key: "{{ .mysecret | pkcs12key }}"
 
   data:
   # this is a pkcs12 archive that contains