feat(lsp): show jump target picker when multiple definitions are found

[MatrixNeoKozak]

What

Fixes #3093: When an LSP server resolves a position to multiple definitions (e.g. obj.sayHello() where obj can be one of several classes overriding the method, including the base class), the old code silently jumped to the LAST entry (msgObj[msgObj.length - 1]), which is arbitrary and confusing.

Now, when more than one jump point is returned:

• A ModalBar picker is shown listing every candidate as a file:line:col button (jQuery .text() is used, so labels are HTML-safe).
• Clicking a target performs the actual jump (open file if needed, then move the cursor).
• Dismissing the bar (Esc / clicking elsewhere) rejects the deferred so the NAVIGATE_JUMPTO_DEFINITION command promise always settles.
• Single-definition results behave exactly as before.

The jump logic was factored into a shared jumpToLocation helper so the picker path and the single-result path stay identical. The picker prompt is added to src/nls/root/strings.js for translation.

Why

This change resolves the target issue or improvement.

How to test

Verify that the project builds/runs correctly and the specific bug/improvement is addressed.

Fixes #3093

[sonarqubecloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[abose]

Thanks @MatrixNeoKozak for contributing this! Could you also attach a screenshot of the current UI changes to the PR?

For this workflow, a ModalBar isn't quite the UX we were intending. When a user Ctrl-clicks to jump to a definition, or invokes it using the Ctrl+J keyboard shortcut, showing the choices in a bar at the top of the editor means the user may have to move their attention and mouse all the way to the top to select a target. It also makes the flow less natural for users who started the action entirely from the keyboard.

A better approach would be to show a Code Hints-style dropdown near the current cursor position, listing the possible jump targets along with a short description/context for each one.

This would keep the interaction close to where the user is working and, importantly, the existing Code Hints dropdown is already designed to be keyboard-accessible, so users should be able to navigate and select a target without leaving the keyboard.

Thanks again for working on this!

[abose]

Superseded by #3118 as we had a different ux implementation for this and a lot of test coverage was needed.

Thanks for contributing @MatrixNeoKozak and apologies for not being able to merge this as it needed a lot of work to adhere to our ux. We can provide the ux design guides in the future if you would like to work on this, just comment back when we have any questions and will support you. Thanks again for the support!