BugFix: Fix the flaky test case

Issue Description

1 failing
  1) Tasks
       PATCH /tasks
         Should add startedOn field when assignee passed as a payload:
      AssertionError: expected 1731347350 to equal 1731347351
      + expected - actual
      -1731347350
      +1731347351
      
      at Context.<anonymous> (test/integration/tasks.test.js:769:50)
      at Generator.next (<anonymous>)
      at fulfilled (test/integration/tasks.test.js:4:58)
      at processTicksAndRejections (node:internal/process/task_queues:95:5)

This test case fails randomly, and passes on re-running it

Expected Behavior

• The test case shouldn't fail any time. We should fix the logic of this test case, as due to this flaky test, people can sometime ignore the genuinely failing test cases too.

Current Behavior

Screenshots

Reproducibility

• This issue is reproducible
• This issue is not reproducible

Steps to Reproduce

Severity/Priority

• Critical
• High
• Medium
• Low

Additional Information

Checklist

• I have read and followed the project's code of conduct.
• I have searched for similar issues before creating this one.
• I have provided all the necessary information to understand and reproduce the issue.
• I am willing to contribute to the resolution of this issue.

Start with test/integration/tasks.test.js at line 769 and run the PATCH /tasks integration test for the startedOn assertion. Inspect how the expected and actual timestamps are produced, then verify the test passes reliably across repeated runs without masking genuine failures.