Incorrect timestamp generation may lead to saving outdated TestRunStatus results

Incorrect timestamp generation may lead to saving outdated TestRunStatus results.

1) User deletes a Test Execution from Test Plan. Test Plan has a Test which is included in that Test Execution.

2) Thread T1 is generated, it makes a test run status calculation which may take a while depending on how much information (example: scopes) it need to consider.

3) Immediately after, user imports another PASSING execution (with the same Test) into the Test Plan. Thread T2 is generated.

4) While T2 has already finished the calculation and saves its PASS result in the TestRunStatus table, T1 finishes and removes the previous PASS result from the TestRunStatus.

At this point the Test Plan is incorrect: The Test Plan Status bar is TODO, the latest status for the Test is TODO but the Test has one execution in the Test Plan scope has PASS.