Remove faulty progress bar for remote write-back

As write-back uses a different jobId the computation jobId is wrong to use for update

Author: FlorentinD

graphdatascience/query_runner/session_query_runner.py

@@ -202,12 +202,13 @@ def run_write_back() -> DataFrame:
             return write_protocol.run_write_back(self._db_query_runner, write_back_params, yields, terminationFlag)
 
         try:
-            if self._resolve_show_progress(logging):
-                database_write_result = self._progress_logger.run_with_progress_logging(
-                    run_write_back, job_id, database
-                )
-            else:
-                database_write_result = run_write_back()
+            # Skipping progress for now as export has a different jobId
+            # if self._resolve_show_progress(logging):
+            #     database_write_result = self._progress_logger.run_with_progress_logging(
+            #         run_write_back, job_id, database
+            #     )
+            # else:
+            database_write_result = run_write_back()
         except Exception as e:
             # catch the case nothing was needed to write-back (empty graph)
             # once we have the Arrow Endpoints V2, we could catch by first checking the jobs summary