fix(lsp): handle URI in item_to_location

[lawrenceho]

Description

Following up on my comment in #3137 regarding the broken jump to Java classes such as java.lang.String because the JDT URI is not a file name. With item.filename being jdt:https://contents/java.base/java.lang/String.class..., the call vim.uri_from_fname(item.filename) in item_to_location would convert the JDT URI into an invalid URI by adding file:https:// in front of jdt:https:// and encode the already encoded URI again. The jump would fail as a result.

This is an attempt to fix the issue by applying filename to URI transformation only if item.filename is not a URI.

Error message:

Error executing vim.schedule lua callback: /usr/share/nvim/runtime/lua/vim/lsp/util.lua:1136: Cursor position outside buffer
stack traceback:
	[C]: in function 'nvim_win_set_cursor'
	/usr/share/nvim/runtime/lua/vim/lsp/util.lua:1136: in function 'jump_to_location'
	...nvim/lazy/telescope.nvim/lua/telescope/builtin/__lsp.lua:197: in function 'handler'
	/usr/share/nvim/runtime/lua/vim/lsp/client.lua:685: in function ''
	vim/_editor.lua: in function <vim/_editor.lua:0>

Type of change

• Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list relevant details about your configuration

• Test a jump to java.lang.String (JDT URI handled by nvim-jdtls)
• Test a jump to normal Java source file in workspace
• Test a jump to normal Lua source file in workspace

Configuration:

• Neovim version (nvim --version):
  NVIM v0.10.0
  Build type: RelWithDebInfo
  LuaJIT 2.1.1707061634

• Operating system and version:
  Linux (Fedora 40)

Checklist:

• My code follows the style guidelines of this project (stylua)
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation (lua annotations)

[Conni2461]

does everything still work, i sadly cant test this because i dont use jdt? if yes i am going to merge, thanks for the fix :)

[lawrenceho]

does everything still work, i sadly cant test this because i dont use jdt? if yes i am going to merge, thanks for the fix :)

Yes, it works fine with the latest change, thanks!

[Conni2461]

Thanks :)