Option --experimental_enable_label_completions causes starpls to hold Bazel lock on every BUILD file change

[olafurpg]

Thank you for building a great Bazel BSP! We have --experimental_enable_label_completions enabled for all usrs in a large monorepo and I've observed that whenever I edit BUILD files, the message "Refreshing all workspace targets" appears in the VS Code status bar and this process appears to hold onto a Bazel lock. I believe I've tracked this down, and disabling --experimental_enable_label_completions stop the behavior.

Would it be possible to somehow debounce the target syncing to minimize the time the language server holds onto the bazel lock? A workaround is to disable the experimental flag for now.