Neovim integration does not work with Remote-SSH

Describe the bug
Neovim integration does not work in workspaces that are from a remote host connected with Remote-SSH plugin. An error is thrown:

Configuration: Invalid neovimPath. The argument 'file' cannot be empty. Received ''.

and both :g and :norm does not work. (Command :g[lobal] is not yet implemented (PRs are welcome!))

Both the local host and remote host is installed with neovim 0.8.0.

Setting "Neovim Path" to the local nvim path C:\Program Files\Neovim\bin\nvim.exe makes nvim integration work for local workspaces but remote workspaces are still the same. (:g not working, same error message)

Setting "Neovim Path" to the remote nvim path /usr/bin/nvim makes nvim integration not work both locally and remotely. Same error message:

Configuration: Invalid neovimPath. The argument 'file' cannot be empty. Received ''.

I have double-checked both nvim executable path and they are both correct. (Can launch neovim with the said full path.)

To Reproduce
Steps to reproduce the behavior:

1. Enable neovim integration in Settings, set "Neovim Path" to either local nvim executable path or remote nvim executable path
2. Use Remote-SSH plugin to connect to a remote host
3. Open any remote file, type ':g'
4. Command :g[lobal] is not yet implemented (PRs are welcome!)

Expected behavior
Neovim should ideally work in remote-ssh workspaces and ideally uses the remote instance of nvim.

Environment (please complete the following information):
VSCode 1.73.1
VSCodeVim v1.24.3
Remote - SSH v0.96.0
Local OS: Windows 10 21H2
Remote OS: Linux

Start by reproducing the Neovim integration with a local workspace and a Remote-SSH workspace, using the reported local and remote executable paths. Trace how the "Neovim Path" setting is handled in each workspace and verify the :g and :norm entry points; done means the remote workspace uses its remote Neovim instance without the empty-path error.