feat(orggatekeeper): [#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/orggatekeeper/deployment.yaml

@@ -59,9 +59,10 @@ spec:
             - name: SENTRY_ENVIRONMENT
               value: {{ .Values.sentry.environment | quote }}
             {{ end }}
-          envFrom:
-            - configMapRef:
-                name: orggatekeeper-config
+            {{- range $name, $value := .Values.orggatekeeper.environment }}
+            - name: {{ $name }}
+              value: {{ $value | quote }}
+            {{- end }}
           ports:
             - containerPort: 8000
           resources: