Avoid running bundler commands before running custom bundle logic

[vinistock]

Motivation

I believe these are the issues reported here #664 (comment).

We can't make any bundler inquiries before starting the server. Now that the custom bundle logic runs on the server, the bundle will only be installed after the server booted successfully. Trying to read the server version before starting will always fail if the gems aren't installed (because we haven't run bundle install yet).

Additionally, we need to fully deprecate Ruby 2.7. Because the gem now requires Ruby >=3.0, using gem install ruby-lsp will never install v0.7.3, which means it's impossible to use the extension with Ruby 2.7.

Implementation

• Moved the server version check after the custom bundle logic
• Changed the Ruby version check

[st0012]

Unfortunately I can't reproduce the issue I saw anymore, so I can't confirm that it'd be fixed with the change. But I think it's likely that the issue was caused by the mentioned problem 👍

[andyw8]

Additionally, we need to fully deprecate Ruby 2.7

We should make sure to highlight this in the release notes.

[st0012]

@vinistock Would the Ruby 2.7 error be raised to users who specify ruby-lsp versions in Gemfile too?

[vinistock]

Yes. This is a complete drop of 2.7.