Path config-less summary computation for library modules

[toinehartman]

Describe the bug

Currently, summary computation requires a path config. Path configs are only applicable to source projects, so for library projects, this is confusing and might introduce errors.

Change summary computation for library modules to not compute path configs.

Preparing work on Rascal: usethesource/rascal#2748
Related issues:

• Path config computation is incorrect for std rascal#2743
• Project root computation fails for modules in std:// #968

To Reproduce

Steps to reproduce the behavior:

1. Open a module with stdlib imports.
2. Trigger a type-check.
3. Go-to-def on import IO (or similar)
4. In the opened standrad library module, go-to-def on some reference again.
5. Observe the path config in the debug console; it has a project root in std://, jar+file:// or mvn://

Expected behavior
Do not compute a path config for binary modules.

Desktop (please complete the following information):

• Context: VS Code extension
• Rascal Version: LSP 2.22.3