Add NoExecute toleration for mariadb and rabbitmq

This patch moves the NoExecute toleration for mariadb
and rabbitmq pods to the new toleration parameter.

NoExecute toleration is required because of:
https://review.opendev.org/c/starlingx/openstack-armada-app/+/751358

Story: 2009232
Task: 44151

Signed-off-by: Hugo Brito <hugo.brito@windriver.com>
Change-Id: I09d109f5725d60ef1d670c62055b98f99a194eb0

stx-openstack-helm/stx-openstack-helm/manifests/manifest.yaml

@@ -199,6 +199,8 @@ data:
           - key: node-role.kubernetes.io/master
             operator: Exists
             effect: NoSchedule
+          - effect: NoExecute
+            operator: Exists
     conf:
       ingress_conf:
         worker-processes: '4'
@@ -207,9 +209,6 @@ data:
           [mysqld]
           wait_timeout=3600
           wsrep_provider_options="gmcast.listen_addr=tcp://0.0.0.0:{{ tuple "oslo_db" "direct" "wsrep" . | include "helm-toolkit.endpoints.endpoint_port_lookup" }}"
-    tolerations:
-      - effect: NoExecute
-        operator: Exists
   source:
     type: tar
     location: http://172.17.0.1/helm_charts/starlingx/mariadb-0.2.5.tgz
@@ -364,6 +363,8 @@ data:
           - key: node-role.kubernetes.io/master
             operator: Exists
             effect: NoSchedule
+          - effect: NoExecute
+            operator: Exists
       probes:
         readiness:
           periodSeconds: 30
@@ -375,9 +376,6 @@ data:
     # filesystem race as seen in the LP.
     volume:
       size: 1Gi
-    tolerations:
-      - effect: NoExecute
-        operator: Exists
   source:
     type: tar
     location: http://172.17.0.1/helm_charts/starlingx/rabbitmq-0.1.13.tgz