feat(task-reporter): add reporter field to task data structure

- Introduced a new 'reporter' field in the task data structure for both backend and frontend task management.
- Updated the tasks-controller to include the reporter information when transforming task data.
- Modified the fetchTasks and fetchTasksV3 functions to handle the reporter field, ensuring it defaults to undefined when not present.

worklenz-backend/src/controllers/tasks-controller-v2.ts

@@ -1161,6 +1161,7 @@ export default class TasksControllerV2 extends TasksControllerBase {
         attachments_count: task.attachments_count || 0,
         has_dependencies: !!task.has_dependencies,
         schedule_id: task.schedule_id || null,
+        reporter: task.reporter || null,
       };
     });
 

worklenz-frontend/src/features/task-management/task-management.slice.ts

@@ -189,6 +189,7 @@ export const fetchTasks = createAsyncThunk(
           attachments_count: task.attachments_count || 0,
           has_dependencies: task.has_dependencies || false,
           schedule_id: task.schedule_id || null,
+          reporter: task.reporter || undefined,
         }))
       );
 
@@ -302,6 +303,7 @@ export const fetchTasksV3 = createAsyncThunk(
           attachments_count: task.attachments_count || 0,
           has_dependencies: task.has_dependencies || false,
           schedule_id: task.schedule_id || null,
+          reporter: task.reporter || undefined,
         };
         
         return transformedTask;