Install vim and use it over SSH is the easiest and most direct approach. Since the editor runs in text mode it's perfectly happy to work over SSH. Use tailscale and you can get secure, global access from anywhere like they seem to do with vscode.dev creating a tunnel (tailscale even just added explicit SSH support: https://tailscale.com/blog/tailscale-ssh/).
This is basically how I operate most of the time. I ssh from my laptop to a bastion jump node and then ssh to my instance in EC2 where I do all my work in tmux and vim.
It's cheap, reliable, easy and it works like it did 20 years ago so it's completely network issue resilient as I can just attach to tmux again if something borks.
I've worked with some former Pivotal folks, and this is the main workflow they use, especially for pairing. Start a tmux session on a remote host and have two folks SSH in and connect to the same tmux session and they will see the exact same thing, and both have full keyboard control.
Alternatively the vscode-neovim plugin actually embeds a headless neovim inside vs code: https://github.com/vscode-neovim/vscode-neovim It's perhaps a bit more complete and featureful vs. the other plugin (like it can run all the same plugins and lua config as neovim) but IMHO it's kind of confusing and weird to have two editors running at once, configured independently.