test(fuse): a listing from before a create commits keeps the landed file (B166)

The account run's 0-byte read of a new file was B166 too: Drive's
listing had the node from before its create was committed, and the
queue no longer held it when read. The fake Drive can now hold a
folder's listing on its way back with one file listed unrevised.

docs/CHANGELOG.md

@@ -59,8 +59,9 @@ by its local id, in the queue, the stored tree and pins alike.
   upload landed showed it both as Drive had it and as the queue did (B164).
 - **Stopping the daemon no longer hangs until systemd kills it.** A stop waits up to 10 s for
   work in progress, then exits and logs what was still running (B165).
-- **A folder no longer drops a new file while others are uploaded.** A file whose upload
-  landed while the folder was being listed was missing from that listing (B166).
+- **A folder no longer drops or empties a new file while others are uploaded.** A file whose
+  upload landed while the folder was being listed was missing from that listing, or listed as
+  empty (B166).
 - **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).
 - **A change that waits for a name to be freed no longer waits seconds after it is.** A rename or