docs: Update editor support (#54)

* docs: link to new repos for editor support

This also temporarily removes removes emacs support as it needs to be
updated to support raw strings before we take it over.

* docs: remove other tooling not currently ported for Alloy

Other tooling, such as the treesitter grammar, is not officially
maintained by the Alloy developers and so it's being temporarily removed
from the documentation until an Alloy equivalent exists that we can link
to.

docs/sources/concepts/config-language/_index.md

@@ -109,18 +109,10 @@ The preceding example has two blocks:
 
 You can use one or all of the following tools to help you write configuration files in River.
 
-* Experimental editor support for
-  * [vim](https://github.com/rfratto/vim-river)
-  * [VSCode](https://github.com/rfratto/vscode-river)
-  * [river-mode](https://github.com/jdbaldry/river-mode) for Emacs
+* Editor support for:
+  * [VSCode](https://github.com/grafana/vscode-alloy)
+  * [Vim/Neovim](https://github.com/grafana/vim-alloy)
 * Code formatting using the [`agent fmt` command][fmt]
 
-You can also start developing your own tooling using the {{< param "PRODUCT_ROOT_NAME" >}} repository as a go package or use the
-[tree-sitter grammar][] with other programming languages.
-
 [RFC]: https://github.com/grafana/agent/blob/97a55d0d908b26dbb1126cc08b6dcc18f6e30087/docs/rfcs/0005-river.md
-[vim]: https://github.com/rfratto/vim-river
-[VSCode]: https://github.com/rfratto/vscode-river
-[river-mode]: https://github.com/jdbaldry/river-mode
-[tree-sitter grammar]: https://github.com/grafana/tree-sitter-river
 [fmt]: ../../reference/cli/fmt/