removed replicas: 1 from mariadb deployment

Setting `replicas: 1` on the mariadb deployment causes problems
in our sandbox environment where an idler scales down workloads
to save costs. The idler and the ReplicaSet fight, which causes
the mariadb pod to start and stop infinitely, which eventually
leads to InnoDB corruption. For now, solve by not setting
`replicas: 1` so that the idler wins.

Fixes: https://issues.redhat.com/browse/RHODS-7771

Author: gregsheremeta

config/internal/mariadb/deployment.yaml.tmpl

@@ -8,7 +8,6 @@ metadata:
     app: mariadb-{{.Name}}
     component: data-science-pipelines
 spec:
-  replicas: 1
   strategy:
     # Need this since backing PVC is ReadWriteOnce,
     # which creates resource lock condition in default

controllers/testdata/declarative/case_0/expected/created/mariadb_deployment.yaml

@@ -8,7 +8,6 @@ metadata:
     app: mariadb-testdsp0
     component: data-science-pipelines
 spec:
-  replicas: 1
   strategy:
     type: Recreate  # Need this since backing PVC is ReadWriteOnce, which creates resource lock condition in default Rolling strategy
   selector:

controllers/testdata/declarative/case_2/expected/created/mariadb_deployment.yaml

@@ -8,7 +8,6 @@ metadata:
     app: mariadb-testdsp2
     component: data-science-pipelines
 spec:
-  replicas: 1
   strategy:
     type: Recreate  # Need this since backing PVC is ReadWriteOnce, which creates resource lock condition in default Rolling strategy
   selector: