control-service: fix data jobs builds

Change the way the success of a data job build is
evaluated since newer version of K8s notify
earlier with different job conditions.

Signed-off-by: Dako Dakov <ddakov@vmware.com>

Author: ddakov

projects/control-service/projects/pipelines_control_service/src/main/java/com/vmware/taurus/service/KubernetesService.java

@@ -1196,15 +1196,15 @@ private JobStatusCondition getJobCondition(V1Job job) {
             c.getType(),
             c.getReason(),
             c.getMessage());
-        if (c.getType().equals("Complete") || c.getType().equals("SuccessCriteriaMet")){
+        if (c.getType().equals("Complete") || c.getType().equals("SuccessCriteriaMet")) {
           return new JobStatusCondition(
-                  c.getType().equals("Complete") || c.getType().equals("SuccessCriteriaMet"),
-                  c.getType(),
-                  c.getReason(),
-                  c.getMessage(),
-                  c.getLastTransitionTime() != null
-                          ? c.getLastTransitionTime().toInstant().toEpochMilli()
-                          : 0);
+              c.getType().equals("Complete") || c.getType().equals("SuccessCriteriaMet"),
+              c.getType(),
+              c.getReason(),
+              c.getMessage(),
+              c.getLastTransitionTime() != null
+                  ? c.getLastTransitionTime().toInstant().toEpochMilli()
+                  : 0);
         }
       }
     }