feat(definition): go to dependency

[mhanberg]

This enables the tracers when your dependencies are compiling, which adds them to the symbol table.

TODO

• Make sure that they do not show up in Workspace Symbols
• see if we need/can show the progress message when the database is finishing a "batch" of updates (message can say "indexing"). It can get bogged down and the go to def won't work until it's done inserting.
• tests
• determine feasibility for elixir source files. they won't exist on disk, and since they aren't compiled, we won't have symbols for them, but there might be the possibility of opening the line of code in github in their web browser.

cc @dvic, feel free to take this over if you'd like!

Closes #91

[dvic]

determine feasibility for elixir source files. they won't exist on disk, and since they aren't compiled, we won't have symbols for them, but there might be the possibility of opening the line of code in github in their web browser.

If you use ASDF and build Elixir from source (i.e., use elixir ref:v1.15.4 instead of elixir 1.15.4-otp26) then the source code navigation works just fine in ElixirLS. I guess we can support this for now?

cc @dvic, feel free to take this over if you'd like!

sure :) I'll give it a go!

[mhanberg]

ElixirLS uses the elixir sense project instead of only elixir core, which gives it other capabilities.

If we can determine the function/module using the Code.Fragment module and it's path, then should be good.

[mhanberg]

• make sure dependencies don't show up in Find References

[mhanberg]

Superceded by #171