control-service: use newest job image builder (#3226)

# Why
We are using a very old job builder image. 
The newer releases are much faster at building. 

However importantly the new versions don't work with VDK server. 
VDK server uses a git without ssl enabled and this causes issues for the
new jobs builders.
SO for the moment vdk server will keep using the old version. 

# How was this tested? 
deployed to k8s and everything works perfectly.

---------

Co-authored-by: paulm2 <paulm2@vmware.com>

Author: murphp15

projects/control-service/projects/helm_charts/pipelines-control-service/values.yaml

@@ -52,7 +52,7 @@ operationsUi:
 deploymentBuilderImage:
   registry: registry.hub.docker.com/versatiledatakit
   repository: job-builder
-  tag: "1.2.3"
+  tag: "1.4.1"
   username:
   password:
 

projects/vdk-plugins/vdk-server/src/vdk/plugin/server/installer.py

@@ -709,6 +709,8 @@ def __helm_install_command(self, git_server_ip):
             "datajobTemplate.template.spec.successfulJobsHistoryLimit=5",
             "--set",
             "datajobTemplate.template.spec.failedJobsHistoryLimit=5",
+            "--set",
+            "deploymentBuilderImage.tag=1.2.3",
             "-f",
             self.__current_directory.joinpath("helm-values.yaml"),
         ]