Option to include external libraries into context

[jakethekoenig]

When implementing something, it happens a lot (>20% of cases) that the LLM tries to use outdated function names of an external library.

When this happens, there should be an option to include the external library in the context as well in order for the LLM to understand how to use it properly.

For example, a Ruby project might have a few files in it, one of which would try to use an external library Eth::Utils.bin_to_hex. But since the LLM was trained, the naming has changed slightly and now it's Eth::Util.bin_to_hex (no "s"). Since Eth is an external library and is not placed in the project directory, mentat has no access to it and doesn't inject it into the context.

To fix it, we can add some way to access the external library (which is already on the local drive but not inside of the current directory) into context.

@mentatbot can you figure this out please?

[jakethekoenig]

@mentatbot

[jakethekoenig-testbot[bot]]

I will start working on this issue