Please add an option for the remote nvim to use its own existing config

[yacoob]

Is your feature request related to a problem? Please describe.
I use remote-nvim with devpod. My devcontainers are built on top of ghcr.io/yacoob/interactive:devenv, which brings my dotfiles, neovim and a couple of tools. Effectively, my devcontainer already comes with neovim+config prepared.

Describe the solution you'd like
I'd like remote-nvim to just use the nvim on the remote as-is, without creating a separate vim runtime on the remote. Right now, during a remote-nvim workspace setup I can skip nvim installation and skip config copy - but the resulting configuration will use a dedicated rtp and NOT use the existing config.

Describe alternatives you've considered
I guess I can parachute in after remote-nvim sets things up and symlink that remote workspace's vim config to the one the container brings?