Make the VSCode extension also launch on Obj-C/C++

[rockbruno]

https://github.com/swiftlang/vscode-swift only launches when opening a Swift file, but sourcekit-lsp (and by extension our BSP) also works for Obj-C and C++.

[Clemo97]

Hello @rockbruno and @luispadron

I heard about this project when i was working on another issue on the swift sourcekit-lsp, and I was intrigued swiftlang/sourcekit-lsp#2276 (comment) .

I'm interested in contributing to this project and want to better understand its scope and intended use cases. I've read through the README and explored the codebase, but have some clarifying questions that would help me contribute more effectively.

1. From what I understand, sourcekit-bazel-bsp bridges sourcekit-lsp and Bazel to enable iOS development in editors like VSCode/Cursor for Bazel-based projects,
   What's the typical developer journey? (e.g., "I'm on a team using Bazel for iOS and want better IDE flexibility")

2. Swift Package Dependencies
   The README mentions this works with Bazel projects, but I'm unclear on Swift package integration:

   Questions:

• Does sourcekit-bazel-bsp automatically recognize Swift SDKs?
• If I have an existing Bazel iOS project that uses SPM dependencies (converted via rules_swift_package_manager), should code completion, jump-to-definition, etc. "just work" for those dependencies?

3. Existing iOS App Migration

   Question:

• Is there any guidance on migrating existing Xcode projects to work with sourcekit-bazel-bsp? Or is the expectation that teams already have a working Bazel setup?

[luispadron]

@Clemo97 Hey! More contributions are always welcome.

1. Xcode doesn't scale well, even with Bazel. Also, with AI tools now becoming more widely available in editors like VSCode/Cursor a lot of devs want to use their text editor of choice on bazel + iOS projects.

2. It finds the required paths via the normal Bazel-Xcode toolchain stuff from rules_swift. Yes, SPM deps via rules_spm should just work as they're just normal external dependencies in Bazel.

3. There's some guides on Bazel migration on the internet and in rules_apple docs but that might be out of scope for this project. The end goal though (at least for me) is that we get this BSP to the point where it just works with minimal to no setup in an existing Bazel project.