Make workspace/buildTargets reply meaningful information #28
Description
Currently, we only provide SourceKit with some very basic information about Swift libraries, which is why many features currently either do not work or don't work very well (like how jump to definition can throw you to Bazel's output base).
The solution to this is to reply more solid and correct information to this request, such as which files are generated, which targets are test targets, passing to SourceKit the right index import mapping regexes, and so on. We should also have the example project contain all of the different cases this request can handle in order to demonstrate and prove its functionality.