feat: patch Deployment env vars directly via k8s API (v1.3.78)

Fission newdeploy executor does NOT apply fn.Spec.PodSpec when building
Deployment spec - it only uses env.Spec.Runtime.Container and podSpecPatch.

Fix: after updating Function CRD, also directly patch the newdeploy
Deployment via Kubernetes API using StrategicMergePatch, searching by
labels functionName/functionNamespace/executorType=newdeploy.

This ensures env vars immediately appear in the container and survive
pod scaling events (scale to 0 / scale back to 1).

console/deploy/console.yaml

@@ -55,7 +55,7 @@ spec:
       serviceAccountName: fission-console
       containers:
         - name: console
-          image: naeel/fission-console:v1.3.77
+          image: naeel/fission-console:v1.3.78
           imagePullPolicy: Always
           ports:
             - containerPort: 8090