Migrate chruby activation to the new version manager implementation

[vinistock]

Motivation

The changes in Shopify/vscode-ruby-lsp#923 were useful for testing purposes, but I think we cannot have a blanket implementation that will work for every version manager. Clearly, they each have their own specificities that need to be accounted for with care (e.g.: Mise supports multiple level of hierarchy in configuration and RVM supports the .ruby-gemset file).

To move forward with more confidence, I'm proposing a similar approach, with a redesign, so that we can ship this as part of our stable releases.

Implementation

The idea of the implementation is that

• We keep the version manager setting, so that people can specify what they are using
• We make each version manager a separate class, which is responsible for processing the configuration files and finding the Ruby installation directory (which are both different in most managers)
• The parent version manager enforces what needs to be implemented by each version manager and puts all the pieces together to activate the Ruby environment

This way, we can also move slowly and ship one version manager at a time, gathering feedback as we go.

This maintains the similar advantages of the other PR, such as fully decoupling from shells and allowing us to have extensive testing for each manager. Additionally, this PR implements most of the shared behaviour, so the next managers should be easier to implement.

Automated Tests

Added tests for chruby.

Manual Tests

1. Launch the extension in a project using chruby
2. Verify that the LSP launches correctly

[st0012]

🎩 👌

[andyw8]

Could this be in the parent class? Since I expect we'll have something similar for other managers.

[vinistock]

Let's wait a bit until we have more managers using this format. The issue is that some of them will be implemented directly in TypeScript and others will just invoke an executable. For the executable ones, printing the entire environment is too large and not very useful.

[andyw8]

Tophatted against factory_bot

That repo doesn't have a .ruby-version file, so it initially detected my ~/.ruby-version, as it should.

I then added a .ruby-version with a different version and restarted the LSP, and it picked that up.

[tvdeyen]

This broke chruby detection for me. I HAVE a .ruby-version in my repo (a gem, not a Rails app) and I have a global ~/.ruby-version file in my home folder. It works everywhere, but not with this version of the ruby-lsp extension in latest VSCode. It was working perfectly until this change.

[tvdeyen]

Next person googling here I pinned the extension to 0.5.12 and the issue is gone.

https://stackoverflow.com/questions/42626065/vs-code-how-to-rollback-extension-install-specific-extension-version