C3LSP Fails to Initialize if Workspace is Missing test/ Subdirectory

**Describe the bug** The **c3lsp** extension fails to initialize and report diagnostics if the current workspace directory does not contain a subdirectory named `test/`. The extension outputs an error log indicating it cannot open this path. Real-time syntax checking (diagnostics) will not work until the user manually creates the required `test/` directory. **To Reproduce** Steps to reproduce the behavior: 1. Create a **new, empty workspace** directory (e.g., `~/c3-project-new/`). 2. Open this new directory in VSCodium (File > Open Folder...). 3. Create a C3 source file (e.g., `main.c3`). 4. Introduce a **syntactically bad line** of C3 code (e.g., a missing semicolon or mismatched parentheses). 5. Open the **Output** panel and select "C3 Language Server" (or similar name). 6. **See error** in the output log: `Can't open the directory 'test/'. Please check the paths. No such file or directory` 7. Note that **no real-time diagnostics** are shown in the editor. **Expected behavior** The C3 Language Server should start successfully and provide real-time syntax checking (diagnostics) for open C3 files, **regardless of whether a `test/` subdirectory exists** in the workspace. **Desktop:** - OS: Archlinux - Editor: VSCodium - vscodium-bin 1.106.37943-1 - c3-lsp-git 0.4.0.r25.gcc358ac-1 **Additional context** I am using the **Error Lens** extension, but the core issue is the failure of the C3 Language Server to start and report diagnostics due to the missing path. Creating the `test/` directory manually resolved the issue and enabled real-time diagnostics.