Ensure default gem path is also in document selector

vscode/src/client.ts

@@ -148,17 +148,27 @@ function collectClientOptions(
     });
   }
 
-  // Because of how default gems are installed, the entry in the `GEM_PATH` is actually not exactly where the files
-  // are located. With the regex, we are correcting the default gem path from this (where the files are not located)
-  // /opt/rubies/3.3.1/lib/ruby/gems/3.3.0
-  //
-  // to this (where the files are actually stored)
-  // /opt/rubies/3.3.1/lib/ruby/3.3.0
   ruby.gemPath.forEach((gemPath) => {
     documentSelector.push({
       language: "ruby",
-      pattern: `${gemPath.replace(/lib\/ruby\/gems\/(?=\d)/, "lib/ruby/")}/**/*`,
+      pattern: `${gemPath}/**/*`,
     });
+
+    // Because of how default gems are installed, the gemPath location is actually not exactly where the files are
+    // located. With the regex, we are correcting the default gem path from this (where the files are not located)
+    // /opt/rubies/3.3.1/lib/ruby/gems/3.3.0
+    //
+    // to this (where the files are actually stored)
+    // /opt/rubies/3.3.1/lib/ruby/3.3.0
+    //
+    // Notice that we still need to add the regular path to the selector because some version managers will install gems
+    // under the non-corrected path
+    if (/lib\/ruby\/gems\/(?=\d)/.test(gemPath)) {
+      documentSelector.push({
+        language: "ruby",
+        pattern: `${gemPath.replace(/lib\/ruby\/gems\/(?=\d)/, "lib/ruby/")}/**/*`,
+      });
+    }
   });
 
   // This is a temporary solution as an escape hatch for users who cannot upgrade the `ruby-lsp` gem to a version that