[FEATURE] Investigate upgrading DuckDB from 1.4.4 to 1.5.0

[erikdarlingdata]

Which component(s) does this affect?

• Full Dashboard
• Lite
• SQL collection scripts
• Installer
• Documentation

Problem Statement

Lite currently uses DuckDB.NET 1.4.4. DuckDB v1.5.0 ("Variegata") was released on March 9, 2025 with several improvements relevant to our embedded usage:

• Concurrent commits during checkpointing — could reduce lock contention between the collector and maintenance
• Concurrent deletes and insertions with indexes during checkpointing — same benefit
• Recovery mode for ATTACH with NO_WAL support — could help with corruption recovery scenarios (Fix DuckDB file corruption during maintenance (#218) #221)
• Block allocator for improved memory management — potential memory footprint reduction
• Late materialization in query execution — potential query performance improvement

Full release notes: https://github.com/duckdb/duckdb/releases/tag/v1.5.0

Proposed Solution

1. Update DuckDB.NET.Data and DuckDB.NET.Bindings.Full from 1.4.4 to 1.5.0 in Lite/Lite.csproj
2. Verify DuckDB.NET has a matching 1.5.0 release on NuGet
3. Test that existing DuckDB databases created with 1.4.4 open correctly (DuckDB handles storage format upgrades automatically, but should verify)
4. Run Lite through a full collection cycle and confirm no regressions
5. Verify maintenance (archive, vacuum) still works correctly

Use Case

Stay current with upstream, benefit from concurrency and memory improvements.

Alternatives Considered

Stay on 1.4.4 — no urgency, but falling behind makes future upgrades harder.

Additional Context

Current packages in Lite/Lite.csproj:

<PackageReference Include="DuckDB.NET.Data" Version="1.4.4" />
<PackageReference Include="DuckDB.NET.Bindings.Full" Version="1.4.4" />