I have checked that this feature is not already implemented

• This feature does not exist

Use case

The Ruby LSP currently unconditionally tries to load add-ons from any ruby_lsp/**/addon.rb file in any installed gem. If you have a gem installed that has such a file, but you don't want the LSP to load its addon, there doesn't seem to be a way around this.

Currently this is just causing noisy logs for me -- I have the tapioca gem installed, and every time the Ruby LSP starts, it prints a stack trace indicating that this version constraint isn't satisfied -- but in principle I'd like to be able to configure which addons the LSP loads or doesn't load.

Description

Allow the user to configure specific addons that the Ruby LSP should load or not load, instead of unconditionally trying to load an addon for every installed gem that has a ruby_lsp/**/addon.rb file.

Implementation

To solve my immediate problem, I'd be fine with a configuration option that lets me specify a deny-list of addons that the LSP shouldn't try to load, but I can imagine a use case for only loading installed addons that occur in an explicitly-specified list.