Unintuitive process for re-enabling VSCode extension after a Ruby update

Description

System: Ubuntu 24.04
Shell: Zsh
Ruby version: 3.3.4
Ruby version manager: rbenv
IDE: VSCode

Reproduction

After updating my project's Ruby version from 3.3.1 to 3.3.4, the extension stopped working with the following error:

2024-08-05 16:22:52.632 [info] (api) rbenv: ruby-lsp: command not found

2024-08-05 16:22:52.648 [info] (api) 
The `ruby-lsp' command exists in these Ruby versions:

2024-08-05 16:22:52.649 [info] (api)   3.2.1
  3.2.2
  3.3.0
  3.3.1

Uninstalling, restarting extensions and reinstalling the extension didn't work.
Closing and reopening the project window did not work (although I didn't fully close vscode, there was another project open, maybe a full restart would have worked?)

Using ctrl+shift+p -> Update language server gem command in VS Code fixed the issue.

I think the extension expected the ruby-lsp gem to be already installed through the custom gemfile inside .ruby-lsp, and wasn't prepared for this. Regular bundle install did nothing because it only works for gems in the project's gemfile.

Ultimately it took me around 20 minutes to figure it out, not a big deal, but it could have been more, and there could be a way to improve this, either through code or documentation

No repository files or tests are named. Reproduce the Ruby 3.3.1-to-3.3.4 update with rbenv in VSCode, compare the failed startup with the successful “Update language server gem” command, and determine whether the fix should be documented or handled by the extension; done means the re-enabling process is clear or works automatically.