fix(otel): increase getSpan start time buffer to 60s for scheduled runs

The schedule engine pre-queues runs ~25s before exactScheduleTime so they're ready to execute on the dot, but overrideCreatedAt stamps the TaskRun's createdAt with the future scheduled time. The getSpan query used createdAt as the window start with only a 1s buffer, causing spans to fall outside the query window for scheduled runs.

The same issue was fixed for getTraceSummary in df4ab97 but getSpan was missed. Applying the same 60s buffer.

Author: matt-aitken

apps/webapp/app/v3/eventRepository/clickhouseEventRepository.server.ts

@@ -1229,7 +1229,7 @@ export class ClickhouseEventRepository implements IEventRepository {
     endCreatedAt?: Date,
     options?: { includeDebugLogs?: boolean }
   ): Promise<SpanDetail | undefined> {
-    const startCreatedAtWithBuffer = new Date(startCreatedAt.getTime() - 1000);
+    const startCreatedAtWithBuffer = new Date(startCreatedAt.getTime() - 60_000);
 
     const queryBuilder =
       this._version === "v2"