If discovery takes a long time (#18200), it seems language server is not started until it has finished, even though it is not "blocked" on discovery NodeJS-wise. This prevents users from using the most basic features like the indexer, so they can't click through functions, variable definitions, etc.

In #18200 the user is blocked for about 15 mins, files are also on a shared network drive.

As language server activations takes less time, I think we can afford to postpone triggering discovery until after it has started. FYI @kimadeline as you're working on the new design to activate/deactivate language servers 🙂

cc/ @karthiknadig