Go to Definition displays error for built-in Apex classes

[randi274]

Summary

Go to Definition support works for user-created Apex classes, but is displaying an error when I try to use this command on built-in Apex classes (like Database).

Steps To Reproduce:

1. Reference a built-in Apex class in your IDE, like Database.insert()
2. Right click the Database class, and select Go to Definition.
3. An error will appear as it tries to navigate to jar:/StandardApexLibrary/System/Database.cls

Expected result

Either no error will appear and we'll say "No definition found" (this is what happens if I use Go to Definition on the insert method), or we'll redirect the user to a faux class that they can use to examine all of the Database methods.

Actual result

Additional information

From examining our LSP, it is the path we're getting back from the Jar. I went back to v47.1.0 (~3 years ago), and we used to just say "No definition found for Database" as well. Then I went back to v52.1.0 (~2 years ago), and this same error pops up, so it's been this way for quite a while. For a bigger lift, we could see about adding these faux classes into our .sfdx directory so the user could examine the methods that we say we support, or redirect the user to our external documentation.

Salesforce Extension Version in VS Code:
v57.7.0 comparing v47.1.0

SFDX CLI Version: 7.183.1

OS and version:
Mac Ventura 13.2.1

[git2gus]

This issue has been linked to a new work item: W-12777249

[lukeis]

fixed with commit 62f0813