feat(sql_export): [#48311] template environment variables directly

Previously, environment variables were templated into a ConfigMap which
was referenced through an `envFrom` in the deployment. Unfortunately,
Kubernetes does not restart deployments on changes to their referenced
ConfigMaps[1], so this indirection means that deployments have to be
restarted manually every time a change is made - something that is very
easy to forget in an otherwise GitOpsy workflow.

[1] kubernetes/kubernetes#22368

os2mo/templates/integrations/sql_export/deployment.yaml

@@ -55,9 +55,11 @@ spec:
                   name: {{ .Values.sql_export.historic_state_secret_name }}
                   key: password
             {{- end }}
-          envFrom:
-            - configMapRef:
-                name: sql-export
+
+            {{- range $name, $value := .Values.sql_export.environment }}
+            - name: {{ $name }}
+              value: {{ $value | quote }}
+            {{- end }}
           ports:
             - containerPort: 8000
           resources: