Add toleration for ptp-notification application

Toleration for the pods composing the application is being added
to this change. The application is composed of a daemonset and a
deployment so the configuration is added on both templates

Tested in an AIO-SX:
- enabled the node taint
- deleted a pod without toleration and observed that the new one
stays in "pending"
- delete the application pods and observed the new ones to reach
"running" state
- remove the node taint
- observe the pending pod reaches "running"

Story: 2009232
Task: 43348

Signed-off-by: Andre Fernando Zanella Kantek <AndreFernandoZanella.Kantek@windriver.com>
Change-Id: I92ce19145efb92847ef59bc5e1ed65cddbe1cf57

stx-ptp-notification-helm/stx-ptp-notification-helm/helm-charts/ptp-notification/templates/daemonset.yaml

@@ -171,3 +171,7 @@ spec:
           hostPath:
             path: /etc/
             type: Directory
+      tolerations:
+      - key: "node-role.kubernetes.io/master"
+        operator: "Exists"
+        effect: "NoSchedule"

stx-ptp-notification-helm/stx-ptp-notification-helm/helm-charts/ptp-notification/templates/deployment.yaml

@@ -23,6 +23,10 @@ spec:
     spec:
       imagePullSecrets:
       - name: {{ .Values.registration.imagePullSecrets }}
+      tolerations:
+      - key: "node-role.kubernetes.io/master"
+        operator: "Exists"
+        effect: "NoSchedule"
 {{- if .Values.registration.affinity }}
       affinity:
 {{ toYaml .Values.registration.affinity | indent 8 }}