Add constraints on MySQL deployment and rebuild

Add constraints because by default MySQL will take a percentage of total
host resources if no constraints is set.

Change-Id: I8c491a6e08fb085fbba689d598536d83ebe3e016

rebuild

@@ -1,3 +1,3 @@
 # This file is used to trigger a build.
 # Change uuid to trigger a new build on every charms.
-c3b9c7c9-2bd4-4df1-a1df-89c729b34eb6
+f0bf8cdb-0b7e-48f1-b669-765b8e4a011f

tests/caas/smoke.yaml.j2

@@ -13,6 +13,7 @@ applications:
     channel: 8.0/stable
     scale: 1
     trust: true
+    constraints: cpu-power=1000 mem=1G
   vault:
     charm: ch:vault-k8s
     channel: latest/edge

tests/ceph/smoke.yaml.j2

@@ -13,6 +13,7 @@ applications:
     channel: 8.0/stable
     scale: 1
     trust: true
+    constraints: cpu-power=1000 mem=1G
   rabbitmq:
     charm: ch:rabbitmq-k8s
     channel: 3.12/edge

tests/core/smoke.yaml.j2

@@ -13,6 +13,7 @@ applications:
     channel: 8.0/stable
     scale: 1
     trust: true
+    constraints: cpu-power=1000 mem=1G
   tls-operator:
     charm: self-signed-certificates
     channel: latest/beta

tests/misc/smoke.yaml.j2

@@ -13,6 +13,7 @@ applications:
     channel: 8.0/stable
     scale: 1
     trust: true
+    constraints: cpu-power=1000 mem=1G
   ldap-server:
     charm: ch:ldap-test-fixture-k8s
     channel: edge