Support Configurable IPC Mechanism (WebSockets, Named Pipes, Stdio) via CLI

[schinnerld]

To enhance flexibility and allow seamless integration with different clients, the Build Server should support configuring the Inter-Process Communication (IPC) mechanism via command-line parameters at startup.

Proposed Enhancement:

• Introduce a CLI parameter (e.g., --ipc=) to specify the IPC type.
• Supported modes:
  • WebSockets – Enables communication over WebSockets.
  • Named Pipes – Uses Named Pipes for local process communication.
  • Stdio – Uses standard input/output for communication.
• Validate input and initialize the selected IPC method accordingly.
• Update usage information

@616b2f: We’re planning to implement this in a fork and submit it via a pull request. Would this workflow be okay for you? Let me know if you have any feedback!

[616b2f]

I didn't planned to support other communication channels, because I didn't had the need for it yet. If you willing to contribute some of those I would appreciate the PRs.

Suggestion to the proposal:

• For the names of the parameters I would suggest to use the same names as the LSP specs describes --pipe=, --port= which would imply the channel type to be used (see https://microsoft.github.io/language-server-protocol/specifications/lsp/3.18/specification/#implementationConsiderations)
• for the implementation details you can also get some inspiration from the roslyn repository, as it was the base for this repo but now supports stdio and named pipes (https://github.com/dotnet/roslyn/blob/main/src/LanguageServer/Microsoft.CodeAnalysis.LanguageServer/Program.cs#L140)