fix(fuse): never adopt a node another queued create is making

A file renamed away from a.txt while its create was on the wire, and a new
a.txt made after it, could both land on the first file's node: the second
create found a fresh, empty a.txt and took it for its own unanswered create.
The first file's rename then carried the second one's bytes away.

A create now leaves alone a node that another create is making under the
same name, and one the tree already knows. It waits for the name like for
any other queued change (docs/BUGS.md B147).

docs/CHANGELOG.md

@@ -44,6 +44,8 @@ are kept.
   A file made a moment before was taken for deleted and dropped from the queue (B145).
 - **A file renamed just as its upload lands keeps its new name.** The tree could take back the
   name Drive still had (B146).
+- **A new file made under a name another file just left no longer takes that file's place on
+  Drive.** Both could land on one node, and one file's content was lost (B147).
 
 ## [2.10.0] — 2026-10-03