Suggestions and thoughts for the wiki entries for vim and neovim

Fix link for neovim wiki entry on https://github.com/james-d-mitchell/gaplint/wiki/ (not sidebar)
Replace word "syntastic" with "ale" with its hyperlink on https://github.com/james-d-mitchell/gaplint/wiki/Using-gaplint-in-neovim (first line; probably a copy and paste error)

Mention alternative installation method of gaplint with pipx which has the advantage of using isolated environments avoiding things like https://xkcd.com/1987/
I am not sure why ale is advertised for neovim and syntastic for vim. Ale works for both as far as I know and syntastic has been marked as archived which IMHO makes syntastic obsolete and should not be used by new users.
IMHO using nvim-lint would be more suitable for neovim: https://github.com/mfussenegger/nvim-lint#custom-linters I would say one can suggest ale for vim and nvim-lint for neovim
What about creating a vim compiler plugin gaplint.vim? This could even be added to upstream vim and neovim. https://github.com/vim/vim/tree/master/runtime/compiler There exist already quite a few linter as compiler plugins: eslint, jsonlint, pylint, and more.
```
if exists("current_compiler")
finish
endif
let current_compiler = "gaplint"

if exists(":CompilerSet") != 2        " older Vim always used :setlocal
command -nargs=* CompilerSet setlocal <args>
endif

" Runs gaplint for current file :h cmdline-special
CompilerSet makeprg=gaplint\ %

CompilerSet errorformat=%f:%l:%m\ [%n]
" ignore unmatched lines
CompilerSet errorformat+=%-G%m
```
Install into $VIM/compiler/gaplint.vim, activate with :comp[iler] gaplint and run :mak or use vim-dispatch with its mapping m<CR>. For this idea see also: https://gist.github.com/romainl/ce55ce6fdc1659c5fbc0f4224fd6ad29

james-d-mitchell / gaplint