Build LSP projects with verbose tracing level

Without that, the language server might trigger awkward warnings about
  unused imports due to trace stripping. So it's better to compile/check
  projects in the language server in the most expanded form.

CHANGELOG.md

@@ -10,6 +10,7 @@
 
 - **aiken-lang**: Fix compiler crash on trace + expect as last expression of a clause. See #1029. @KtorZ
 - **aiken-lang**: Fix redundant warning on introduced identifiers when destructuring validator params. @KtorZ
+- **aiken-lsp**: Compile project using verbose tracing, to avoid having the language server complain about unused imports. @KtorZ
 - **uplc**: Fix (again :grimacing:) cost-models for PlutusV1 & PlutusV2. @MicroProofs
 
 ### Removed

crates/aiken-lsp/src/server/lsp_project.rs

@@ -36,7 +36,7 @@ impl LspProject {
             false,
             u32::default(),
             PropertyTest::DEFAULT_MAX_SUCCESS,
-            Tracing::silent(),
+            Tracing::verbose(),
             None,
         );