Improve lwe startup time

[johnd0e]

Is your feature request related to a problem? Please describe.
Currently at my system it takes about 5s to start.
It's not an issue when start it once, and then use it for long time.
But additional 5s is too long if I want just run some non-interactive one-time request in command line.

Describe the solution you'd like
lwe is pretty complex, as my venv takes ~780MB.
And I'm sure that only small subset of all features are used for simple cases.
May be it's possible not to load all that huge megabytes at once, but only when really needed.

Describe alternatives you've considered
I am understand that this type of request may require too much changes, so...
I just want you to know that for some use cases startup time may be critical.

[thehunmonkgroup]

I just want you to know that for some use cases startup time may be critical.

Then use a library that doesn't leverage the slowest scripting language on earth ;)

I've actually found a great deal of the startup time is taken by the provider plugins. Some of the underlying libraries are probably issuing HTTP requests and such to gather info. There's not a whole lot I can do about that w/o rolling my own provider code, which is not worth it to save a little startup time.

If I disable all plugins, my startup time is about 1.5 seconds.

The design goals of LWE do not include blazing fast startup times. The two main use cases are:

1. Start it and leave it available for quick CLI interaction with LLMs
2. Run more complicated workflows in some kind of automation framework

[thehunmonkgroup]

I'm going to open this back up, because although I personally have no interest in doing the work on this feature, I would review a well-considered PR that improves startup time.