When I saved files in my eslint-formatted projects I was wondering about
slight differences between the results of running `eslint --fix` vs. the
autoamtic formatting when I save a file in neovim.
As it turned out I ran the wrong command indeed. This changes fixes that
by simply calling the correct command on save. Note that this looks
"bigger" but it's actually a copy of the built-in `LspEslintFixAll` of
neovim.
Reference: 1a6d692067/doc/configs.md (eslint)
Reference: 89fd0361b3/lsp/eslint.lua (L92-L104)
Since I use which-key I can actually benefit a lot from meaningful
descriptions of my custom shortcuts. Whenever I feel like I forgot a
multi-key shortcut I can simply type the first letter (in my case
usually "Space" or "g") and peek into the preview of whichkey. It lists
all possible additional keystrokes and their descriptions, so this
change makes it a lot easier for me to find the command I'm looking for.
