Decouple from xcode-build-server #205
Description
Sweetpad is currently tightly coupled to xcode-build-server. For example, when selecting a scheme, it updates the buildServer.json file and overwrites the argv field and other fields that are specific only to xcode-build-server. Sweetpad also seems to restart the Swift LSP server periodically. This restart shouldn’t be necessary for a BSP and it seems to have been added specifically to accommodate xcode-build-server.
This tight coupling makes it almost impossible to use alternative build servers. I’m encountering these issues because I’m using a build server that uses Swift Build for background indexing (similar to Xcode), rather than relying on a full build like xcode-build-server does.
Build servers and Sweetpad serve distinct roles and should ideally operate independently. A BSP is responsible for providing indexing information to SourceKit, while Sweetpad provides a IDE extension for launching, debugging, testing, etc.
It would be great if Sweetpad allowed users to choose their build server, instead of mandating the use of xcode-build-server.