fix(fuse): a file replaced just as its create lands is trashed on Drive (B175)

docs/CHANGELOG.md

@@ -76,6 +76,8 @@ by its local id, in the queue, the stored tree and pins alike.
   there, and the next file with that name no longer became a conflict copy (B173).
 - **Renaming a file just as it reaches Drive no longer fails with "Permission denied"**
   (B174).
+- **A file replaced by a rename just as it reached Drive is removed from Drive too.** It no
+  longer stayed there, and the next rename of its name no longer moved it instead (B175).
 - **A file renamed just as its upload finished keeps its new name.** The mount no longer showed
   the old name, and a second rename no longer failed with "No such file or directory" (B152,
   B172).