v0.0.6

This release fixes an issue with paths to DuckDB files. In short, when filling out the path in the manual connection form, we make it a relative path to the current working directory for ease of use with the most common use case: a user running tbd in the root of their dbt project where the DuckDB file is co-located. The path defined in a dbt profiles.yml is a full path though. Now, if you use a dbt profile for DuckDB, the path pulled from the Profile will remain unedited and stay a full path.