Add case sensitivity to autocomplete #12

Title basically says it all.

With every other language in JetBrains editors, autocomplete is case sensitive, so if I have a struct Thing, and declare const thing: Thing = ..., I then want to call a method on thing and autocomplete shows Thing as the first result.
Similar issue if I have an import from another file and the name of the file is the same as a struct it declares, minus the upper case, and when I start typing the name of the struct and instinctively press tab when it actually first recommends the name of the import, which I don't care about.

This case sensitivity seems like a deliberate choice because I feel like case insensitivity is the default here, as it is with most language support for JetBrains. If that is the case, then I have no idea why anyone would think this is a good idea.

its not a choice by us, auto-completions are handled by ZLS

@ENDERZOMBI102 wrote in #12 (comment):

its not a choice by us, auto-completions are handled by ZLS

Pretty sure it isn't. In Neovim or Zed, this doesn't happen, so it must be editor specific. And it would be weird if JetBrains just didn't allow you to change the case sensitivity. But I guess if that's really the case then I should go bother them or the ZLS team.

LSP4IJ has a client-side option for force-enabling case sensitivity at the client end of the LSP, we could use that

unless theres another option that im missing the LSP4IJ option is... suboptimal. it completely removes completions that are the wrong case rather than just deprioritizing them
image
image

I'll look into a way to add custom sorting logic on top of the lsp4ij autocompletion code for zig/zon files.

We plan on ditching lsp4ij in the next major rewrite of zigbrains and doing all of the autocomplete and stuff inside the plugin directly, so that will give us way more control over stuff like this.

@pentuppup wrote in #12 (comment):

unless theres another option that im missing the LSP4IJ option is... suboptimal. it completely removes completions that are the wrong case rather than just deprioritizing them

That's literally how autocomplete works in JetBrains. That's the behaviour for C with CLion, Rust in RustRover, etc. And I don't see anything wrong with that approach. Just type a capital letter if you want to reference that symbol. Editors like Zed or Neovim show the matching case first but they show the other matches also but personally I don't find that feature to be particularly useful.

if thats how jetbrains normally does it then i suppose that makes, i guess i havent noticed since basically everything in the c++ STL is snake_case. i just find that to be a pretty poor experience, it means you need to know the case of something to find it which isnt great for exploring unfamiliar code