Autocomplete when writing new classes/modules is not very helpful

Description

Reproduction steps

When typing class/module and continuing on, ruby-lsp offers existing classes/modules as autocomplete. This is a nice idea, however I find it highly annoying in basically all cases:

https://github.com/user-attachments/assets/ce69a9db-a5cc-467f-a574-259d0a4b848d

Basically, I can't use enter in most of the cases here and have to either remember to press escape beforehand or undo the autocomplete after it happened.

I think, an ok solution may be to insert what was currently typed as the first suggestion. Or maybe to not offer third-party classes/modules here (but even then you will be at the innermost layer at one point which then will contain an identifier not yet indexed), most of the time you're not reopening third-party classes/modules. Not sure what the best thing to do is, I just know I'm unhappy with how it currently works.

No source file, test, or entry point is identified in the issue. Reproduce the autocomplete behavior while typing a new class or module in ruby-lsp, then define and verify completion behavior that lets Enter preserve the intended text without unwanted existing-class or module insertion.