`git restore` after `git cherry-pick -n` can leave GVFS in a bad state

1. Use git cherry-pick -n to cherry-pick some changes to current branch, leaving them uncommitted
2. Use git restore --staged to unstage the changes

Expected:
All the changes from the cherry-pick move from staged to unstaged in git status.

Actual:
Sometimes some changes disappear from git status.
The files still have the changed contents, but git no longer recognizes the files as being changed.

It's unclear so far whether cherry-pick -n is required or if manual changes with git add will also repro.

git checkout to another branch appears to properly reset the file contents. (I've heard others complain about situations where it did not, though I don't know if they were caused by this and I haven't repro'd that.)

Reproduce the reported sequence with git cherry-pick -n followed by git restore --staged, then compare git status with the files' actual contents. Investigate the conditions under which changed files disappear from status, including whether manual changes followed by git add reproduce it; done means all changes are consistently reported as unstaged.