fix: improve variable naming to avoid shadowing and enhance clarity

- Use epochJob instead of job for epoch-based scheduling to avoid variable shadowing
- Use cronJob instead of job for cron-based scheduling for consistency
- Addresses Copilot suggestions about variable scope and naming clarity

Author: will-dz

core/taskengine/trigger/time.go

@@ -181,7 +181,7 @@ func (t *TimeTrigger) AddCheck(check *avsproto.SyncMessagesResp_TaskMetadata) er
 			}
 
 			cronExpr := t.epochToCron(epoch)
-			job, err := t.scheduler.NewJob(
+			epochJob, err := t.scheduler.NewJob(
 				gocron.CronJob(cronExpr, false),
 				gocron.NewTask(triggerFunc),
 				// In FixedTime, we want to run the job only once
@@ -190,7 +190,7 @@ func (t *TimeTrigger) AddCheck(check *avsproto.SyncMessagesResp_TaskMetadata) er
 			if err != nil {
 				return fmt.Errorf("failed to schedule epoch job: %w", err)
 			}
-			jobs = append(jobs, job)
+			jobs = append(jobs, epochJob)
 		}
 	} else if cronTrigger := check.GetTrigger().GetCron(); cronTrigger != nil {
 		// Handle cron-based scheduling
@@ -214,15 +214,15 @@ func (t *TimeTrigger) AddCheck(check *avsproto.SyncMessagesResp_TaskMetadata) er
 			}
 
 			// Schedule with calculated start time to prevent immediate execution
-			job, err := t.scheduler.NewJob(
+			cronJob, err := t.scheduler.NewJob(
 				gocron.CronJob(cronExpr, false),
 				gocron.NewTask(triggerFunc),
 				gocron.WithStartAt(gocron.WithStartDateTime(nextExecTime)),
 			)
 			if err != nil {
 				return fmt.Errorf("failed to schedule cron job: %w", err)
 			}
-			jobs = append(jobs, job)
+			jobs = append(jobs, cronJob)
 		}
 	}