VS Code Dependency Resolution for Java

I am able to build projects using this extension, but I have not been able to get VS Code to resolve external dependencies using anything that I can find in Bazel build artifacts, BUILD files or anything else. Is there a prescribed way to get VS Code to resolve import statements using anything in the Bazel ecosystem, and the VS Code Java extension pack?

Is there's a way to pull all JARs, I could probably add them as "Referenced Libraries" in the Java Projects extension, for example.

Basically, all of my external `import` statements are unresolved, and I'd like to know how to fix that. I could work on contributing code if this is something the extension could benefit from.

The issue does not name a file, test, or entry point. First investigate how the extension currently exposes Bazel build artifacts and how the VS Code Java extension resolves referenced libraries; define success as external Java imports resolving from Bazel dependencies, then add coverage for that behavior.

Written by the indexing model from the issue text.