:o fails in remote SSH

[ashgillman]

Describe the bug
When I connect to a remote SSH host using Remote-SSH, using :o and then hitting tab for autocomplete results in:

TaskQueue: Error running task. Failed to handle key=<tab>. ENOENT: no such file or directory, scandir '\path\goes\here'.

To Reproduce
Steps to reproduce the behavior:

1. Connect to remote host with Remote-SSH
2. Open a file
3. :o ./
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Environment (please complete the following information):

• Extension (VsCodeVim) version: 1.8.1
• VSCode version: 1.35.0-insider
• Host OS: Windows 10
• Remote OS: Ubuntu 18.04

Additional context
Note that the SSH remote is Ubuntu, could be a contributing issue.

[stevenguh]

Tab completion for :e error out the same way with remote ssh session as well

[stevenguh]

#3639
FYI, this was the pull request for the feature in the first place

[stevenguh]

I looked more into this, and I think this is because the Vim extension is running on the local machine which doesn't have the access of the remote file system and failed at https://github.com/VSCodeVim/Vim/blob/master/src/actions/commands/actions.ts#L1979

EDIT: Maybe using vscode api instead of directly using fs would work?
https://code.visualstudio.com/api/references/vscode-api#workspace.findFiles

EDIT 2: I don't think that findFiles API would work for remote, and there seems to be a proposed API to access file system with any scheme.
https://github.com/Microsoft/vscode/blob/master/src/vs/vscode.proposed.d.ts#L1493

[stevenguh]

I just tested the proposed API. It works for any file connecting scheme like remote ssh.
microsoft/vscode#48034
However, I found the the current codebase for file completion is actually in a bad shape, since it doesn't even work with windows local file completion.