Adding next_run_start_at to the merge conflict, when scheduler updates

Signed-off-by: Yobannys Cabrera Gonzalez <ycabrera@webstaurantstore.com>

.changeset/real-turkeys-report.md

@@ -0,0 +1,5 @@
+---
+'@backstage/backend-tasks': patch
+---
+
+Fixed bug in backend TaskWorker, adding `next_run_start_at` as a merge conflict when scheduler changes

packages/backend-tasks/src/tasks/TaskWorker.ts

@@ -199,7 +199,7 @@ export class TaskWorker {
         next_run_start_at: startAt,
       })
       .onConflict('id')
-      .merge(['settings_json']);
+      .merge(['settings_json', 'next_run_start_at']);
   }
 
   /**