fix: ensure that the entry is already available after remote restore
dino
created
The `RestoreProjectEntryResponse` was simply returning the `entry_id`,
instead of the whole entry information. On the
`RemoteWorktree::restore_worktree` side, the `entry_id` was being used
to obtain the entry, so as to then insert the proto entry, using
`RemoteWorktree::insert_entry`.
Unfortunately, this could lead to panics, for example:
1. Create a new file
2. Undo, which will trash file
3. Redo, which will restore the file
As far as I can tell, this was happening because the `RemoteWorktree`
wasn't yet updated on our end, so there wasn't actually an entry being
returned for `RemoteWorktree::entry_for_id`. As such, this commit
updates the `entry_id` field, and type, in `RestoreProjectEntryResponse`
to the actual `Entry` data, just like in `ProjectEntryResponse`.