feat(readme): clarify _windows_ install recipe

[mattcargile]

Closes #2096
Rework the ordering and create a single command for all deps. Add additional detail on compiler, minimal installs, etc.

I tried to go minimal and maximal in my approach with the collapsed regions. I wanted to try to appease different audiences. The change could very well be to add two pieces of software ( e.g. visualstudio2026buildtools visualstudio2026-workload-vctools to item 2 under the main choco install -y neovim... command.

It is unfortunate a little there is a year in the software name and it would grow stale. Maybe there could be a blurb on how to install it? It is a pretty hard dependency for tree-sitter on Windows from what I can tell. Other options like MSYS2 and Git Bash are substantially more complicated and the users in those environments are probably fairly aware of the tool chain as it is. Having the single choco install command to get all the software in one shot is important for adoption, I think?

Thanks for letting me contribute. Open to any suggestions. :-)

[oriori1703]

Overall looks good, though we might be able to simplify this a bit.

I'm pretty sure that if gcc is available (through mingw) it can be used by nvim-treesitter instead of msvc.
So maybe we can just suggest users install mingw unconditionally, and drop the vs-build-tools entirely.
WDYT?

BTW, sorry for the delay

[nonepork]

Overall looks good, though we might be able to simplify this a bit.

I'm pretty sure that if gcc is available (through mingw) it can be used by nvim-treesitter instead of msvc. So maybe we can just suggest users install mingw unconditionally, and drop the vs-build-tools entirely. WDYT?

BTW, sorry for the delay

Not OP but, the main branch of nvim-treesitter doesn't seem to be able to configure compilers' orders, as it relies on tree-sitter build (which uses cc-rs), and the only way to change it is to modify environment variable CC, as far as I'm aware.

[mattcargile]

Right. The gcc , mingw, and msys2 scenarios are more complex with environment variables and such; not to mention they have separate shells, etc. With Visual Studio build tools with cl.exe, treesitter can find it automatically.

I'll see if I can step through all the scenarios to see what we like the best.