✨ LSP Event & Notification Handling

### Description

Language servers can send clients (CodeEdit) notifications and events we should respond to. These include logging ([[1]](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#logTrace), [[2]](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#window_logMessage)), [show messages](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#window_showMessage), showing [progress](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#window_workDoneProgress_create), [opening a file](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#window_showDocument) and a lot more.

Right now our client implementation receives notifications and events but does nothing with them. This issue is a tracking issue for implementing handlers for each capability a server might use.

Review the existing LSP client implementation and the linked Language Server Protocol specifications for the listed notification and event capabilities. Identify which server messages are currently unhandled, then define the supported handler scope and verification approach for each capability.

Escrita pelo modelo de indexação a partir do texto da issue.