feat: add reloadable LSP logging and setTrace support

[AlexCannonball]

Overview

This PR implements a more idiomatic LSP logging system. It shifts from static file-based logging to a dynamic, reloadable system that communicates directly with the LSP client.

neovim user experience (e.g. via :messages):

VS Code user experience (old output channel):

This will be even better when an Extension uses the modern LogOutputChannel (with options: {log: true}).

Changes

• New log module: Added a custom tracing layer (ClientLogger) that forwards logs to the LSP client via an asynchronous channel.
• Dynamic Filtering: Integrated tracing_subscriber::reload to allow real-time log level updates.
• LSP Protocol Support: Implemented the $/setTrace notification handler in ProtoLanguageServer.
• Unit Tests: Added tests for the new logging layer and level-update logic.

How to test

1. Run the server.
2. From the LSP client, send a $/setTrace notification with value verbose.
3. Observe the desired TRACE and DEBUG logs appearing in the editor's output channel.

Compatibility

I've replaced the previous file-logging implementation to avoid cluttering. Please let me know if you would prefer to keep the file appender as a concurrent logging layer; I can easily add it back as an additional tracing layer.

Fixes #110

[coder3101]

Thanks for your contribution.
Some feedback and rest LGTM

[AlexCannonball]

Thanks for your contribution. Some feedback and rest LGTM

Thank you for your review, I've addressed the comments. Would you like me to squash the commits into one feat: add reloadable LSP logging and setTrace support before merging?