wishlist: bazel support

The classpath script looks like it will work, but it has some caveats. In a monorepo there will be many distinct kotlin targets. IDEA seems to handle this ok, but its not clear how to make sure each target gets a different classpath with this LSP (and noting that we can't assume every target will have the access to all jars, nor even that they will all be of the same version (though that is obviously the common case)).

Figuring out what targets are running kotlin and what their inputs would be is fairly straightforward in bazel (query the action cache and parse the results, then build the input targets.

I'm not sure about timelines, but this is perhaps something we could put together, if there is interest in having the feature.

Start by reviewing the classpath script and how the language server currently determines classpaths. Investigate Bazel action-cache queries and input targets, then define how each Kotlin target receives its own classpath, including targets with different jar access or versions; done means Bazel-backed projects work without assuming one shared classpath.

Written by the indexing model from the issue text.