Add test for retry creation when timed-out task has retryOnTimeoutCount

[vkarpov15]

Motivation

• Add coverage for behavior when an in-progress task times out but has a non-zero retryOnTimeoutCount so a retry task is created.
• Ensure the retry copy resets runtime-specific fields and decrements the retry counter.

Description

• Add a new unit test in test/task.test.js named creates a retry task when a timed out task has retryOnTimeoutCount that simulates an expired in_progress task and calls Task.expireTimedOutTasks().
• Assert the original task moves to timed_out and that a new pending retry task is created with retryOnTimeoutCount decremented.
• Assert the retry task has runtime fields cleared (startedRunningAt, finishedRunningAt, workerName, timeoutAt, error, result) and retains the original scheduledAt and params.
• Assert the retry task's schedulingTimeoutAt is set to now.valueOf() + 10 * 60 * 1000 as expected by the expiry logic.

Testing

• No automated tests were executed as part of this change.
• The change only adds unit test coverage in test/task.test.js and commits it to the branch.

---

Codex Task

[Copilot]

Pull request overview

This PR adds test coverage for the retry mechanism when an in-progress task times out and has a non-zero retryOnTimeoutCount value. The test ensures that the expired task transitions to timed_out status and a new retry task is created with proper field resets and counter decrementation.

Key changes:

• Adds new test case creates a retry task when a timed out task has retryOnTimeoutCount in test/task.test.js
• Verifies retry task creation with decremented retryOnTimeoutCount (from 2 to 1)
• Validates runtime fields are cleared and scheduling fields are properly set

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.