Add some diagnostic logging for ruby-lsp

[marknuzz]

I have checked that this feature is not already implemented

• This feature does not exist

Use case

I think it would be great to have some more support to view diagnostic logs on the ruby-lsp. It seems more important to have that when there are features like formatter autodetection, where you might want to know what formatter is being used, what the command args are, etc.

Description

Show more info in the output window

Implementation

Things like "which formatter was selected, which configuration was used, etc" get shown in the ruby-lsp output window. Maybe this can also be a toggleable feature if there is a concern it is too noisy

[Nakilon]

I wish I could debug why my configuration doesn't apply.

On Sublime Text 4 I tried to disable Rubocop:

{
  "clients": {
    "ruby-lsp": {
      "enabled": true,
      "command": [
        "ruby-lsp"
      ],
      "selector": "source.ruby",
      "initializationOptions": {
        "enabledFeatures": {
          "diagnostics": false,

          "codeActions": false
        },
        "formatter": "none"
      }
    }
  },
  "inhibit_snippet_completions": true
}

I see in LSP logs that it was passed:

  'initializationOptions': {
    'enabledFeatures': {
      'codeActions': False,
      'diagnostics': False
    },
    'formatter': 'none'
  }

but it's still everywhere: