Tooling for vim users

This is a request to give guidance to non-vscode users of Apollo.
Note that the current url `https://www.apollographql.com/docs/devtools/editor-plugins/` is suggestive of being an editor agnostic documentation page.

For vim:
The [coc.nvim](https://github.com/neoclide/coc.nvim) engine has full support for VSCode extensions, so it sounds like we could get vim users the same features as VSCode users for a low overhead (found this article on [how to create a coc.nvim extension](https://medium.com/@chemzqm/create-coc-nvim-extension-to-improve-vim-experience-4461df269173))

Review the current editor plugins page at https://www.apollographql.com/docs/devtools/editor-plugins/ and the linked coc.nvim resources. Determine what Vim users need documented to access the features currently described for VSCode. Done means the documentation clearly explains the Vim/coc.nvim path or its support limitations.

Written by the indexing model from the issue text.