feat(ad_to_mo_sync): [#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.

The `environment_containing_json` does not seem to serve any purpose,
but was probably copied from an old method of templating the ConfigMap
using a for-loop instead of `toYaml`.

[1] kubernetes/kubernetes#22368

os2mo/templates/integrations/ad_to_mo_sync/deployment.yaml

@@ -91,11 +91,14 @@ spec:
               value: {{ required "AD_SEARCH_BASE must be set" .Values.ad_to_mo_sync.ad_search_base | quote }}
             - name: AD_MAPPINGS
               value: {{ required "AD_MAPPINGS must be set" .Values.ad_to_mo_sync.ad_mappings | quote }}
-          envFrom:
-            - configMapRef:
-                name: ad-to-mo-sync-config
-            - configMapRef:
-                name: ad-to-mo-sync-json-config
+            {{- range $name, $value := .Values.ad_to_mo_sync.environment }}
+            - name: {{ $name }}
+              value: {{ $value | quote }}
+            {{- end }}
+            {{- range $name, $value := .Values.ad_to_mo_sync.environment_containing_json }}
+            - name: {{ $name }}
+              value: {{ $value | quote }}
+            {{- end }}
           ports:
             - containerPort: 8000
           resources: