move docstrings, commit openapi spec

[maks-ivanov]

Description

• Enhanced documentation for API types and endpoints with detailed examples and explanations.
• Renamed ReferenceResponse to ReferencesResponse for consistency.
• Improved path handling logic in main.rs and lsp/manager.rs by using full path strings.
• Removed redundant docstring examples to streamline code.

---

Changes walkthrough

	Relevant files
Documentation	api_types.rs Improve API type documentation and naming consistency                    lsproxy/src/api_types.rs Enhanced docstrings for DefinitionResponse and ReferencesResponse. Renamed ReferenceResponse to ReferencesResponse. Removed detailed docstring examples for Symbol, GetDefinitionRequest, and GetReferencesRequest. +39/-75
Enhancement	main.rs Enhance API endpoint documentation and path handling                      lsproxy/src/main.rs Updated docstrings for API endpoints with detailed examples. Changed references from ReferenceResponse to ReferencesResponse. Simplified path handling logic. +63/-25  manager.rs Refactor path handling in LSP manager                                                    lsproxy/src/lsp/manager.rs Improved path handling logic for LSP manager functions. Updated to use full path strings for language detection and client operations. +12/-6

💡 Usage Guide

### Checking Your Pull Request Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later. ### Talking to CodeAnt AI Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code. ### Retrigger review Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

### Check Your Repository Health To analyze the health of your code repository, visit our dashboard at [app.codeant.ai](https://app.codeant.ai). This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.

[codeant-ai[bot]]

Things to consider 🐛

• In the ReferencesResponse struct implementation (lines 206-217), the conversion from Vec<Location> to ReferencesResponse assumes that all Location objects can be directly mapped to FilePosition. If Location objects contain additional data or if the conversion logic is not straightforward, this could lead to incorrect FilePosition mappings or data loss.

• In the definition and references functions, the conversion from the result to DefinitionResponse and ReferencesResponse (lines 351-354) assumes that the from method will handle all edge cases. If the locations vector is empty or contains unexpected data, the response might not be correctly formed, potentially leading to runtime errors or incorrect API responses.