fix(jiva): add serviceAccount name in jiva deployments

required for provision jiva volume deployments in
restricted environment using pod security policy(PSP)

Signed-off-by: prateekpandey14 <prateek.pandey@mayadata.io>

pkg/install/v1alpha1/jiva_volume.go

@@ -72,6 +72,9 @@ spec:
     value: "default"
   - name: VolumeMonitor
     enabled: "true"
+  # ServiceAccountName is the account name assigned to m-apiserver pod
+  - name: ServiceAccountName
+    value: {{env "OPENEBS_SERVICE_ACCOUNT"}}
   # TargetTolerations allows you to specify the tolerations for target
   # Example:
   # - name: TargetTolerations
@@ -872,6 +875,7 @@ spec:
               {{ $sK }}: {{ $sV }}
             {{- end }}
           {{- end}}
+          serviceAccountName: {{ .Config.ServiceAccountName.value }}
           {{- if ne (.TaskResult.sts.applicationName | default "") "" }}
           affinity:
             podAffinity:
@@ -1062,6 +1066,7 @@ spec:
               {{ $sK }}: {{ $sV }}
             {{- end }}
           {{- end}}
+          serviceAccountName: {{ .Config.ServiceAccountName.value }}
           affinity:
             podAntiAffinity:
               requiredDuringSchedulingIgnoredDuringExecution: