fix(slime): render spec.replicas correctly when Values.replicas is 0

Go template truthiness treats numeric 0 as falsy, so the previous
`.Values.replicas` check skipped the `replicas:` block when replicas
was explicitly set to 0. Kubernetes then defaulted the Deployment to
1 replica.

Switch to `(ne .Values.replicas nil)` to distinguish "unset" from
"explicitly 0", matching the existing pattern in the php chart.

Bump chart version 1.3.1 -> 1.3.2 (patch / bugfix).

Refs: SREP-4455

Author: kb-yusukekimura

slime/Chart.yaml

@@ -15,4 +15,4 @@ type: application
 # This is the chart version. This version number should be incremented each time you make changes
 # to the chart and its templates, including the app version.
 # Versions are expected to follow Semantic Versioning (https://semver.org/)
-version: 1.3.1
+version: 1.3.2

slime/templates/deployment.yaml

@@ -15,7 +15,7 @@ metadata:
     {{- toYaml . | nindent 4 }}
     {{- end }}
 spec:
-  {{- if and (not .Values.autoscaling.enabled) .Values.replicas }}
+  {{- if and (not .Values.autoscaling.enabled) (ne .Values.replicas nil) }}
   replicas: {{ .Values.replicas }}
   {{- end }}
   selector: