Fixed the detection of race conditions Due to the instant completions of node moves, and because action packets related to moves are received as a delete+put, it wasn't possible that existing (and not tagged as removed) nodes receive a parent change. Due to file versioning, this is no longer true because a node can become a version when a putnodes is sent. That operation can't use instant completion because the new version doesn't exist yet until the reception of the response from the server. Because of this, the check has been modified to not detect the creation of versions as a race condition by checking the type of the new parent (for a version, it should be a file). Additionally, a new event has been created to monitor these race conditions.
Fixed the detection of race conditions
Due to the instant completions of node moves, and because action packets related to moves are received as a delete+put, it wasn't possible that existing (and not tagged as removed) nodes receive a parent change.
Due to file versioning, this is no longer true because a node can become a version when a putnodes is sent. That operation can't use instant completion because the new version doesn't exist yet until the reception of the response from the server.
Because of this, the check has been modified to not detect the creation of versions as a race condition by checking the type of the new parent (for a version, it should be a file).
Additionally, a new event has been created to monitor these race conditions.

meganz/sdk,Acidburn0zzz/sdk,Acidburn0zzz/sdk,meganz/sdk,meganz/sdk,Acidburn0zzz/sdk,Acidburn0zzz/sdk,Acidburn0zzz/sdk,meganz/sdk,Acidburn0zzz/sdk,meganz/sdk,meganz/sdk,Acidburn0zzz/sdk,Acidburn0zzz/sdk,meganz/sdk