Concurrent operations upon Test Runs statuses (steps, iterations or overall) may produce unexpected results for the user

When the user alters any status within a Test Run (steps, iterations or overall), be it through the UI or through the public REST API, there's a chance that concurrent operations might affect the final result of the intended status update operation. We must find what operations these are and deal with the concurrency problems that might arise from them.