Problem

The Lite DuckDB collection_log table uses server_id which is an integer hash. When reviewing collection results, there's no way to tell which server produced which log entry. This makes diagnosing collection issues (timeouts, errors, performance) difficult.

Expected behavior

Collection log should include the server display name or connection string so entries can be identified at a glance.

Related

Split from investigation during #86. Also relates to #90 (connection timeout diagnostics).