VDK-DuckDB: Introducing a new database plugin

[Maximiliaan72]

Why?

This plugin has been created to check the differences how databases are implemented in a VDK plugin.
The aim of this change is to add DuckDB to the list of database plugins.

What?

I made a new DuckDB-plugin based on the SQLite-plugin.
For making the DuckDB work I had to change several things.
For the Plugin I had to change: Module Imports, Configuration, Connection Factory Method, Ingester Method and Library Specific Code.
For the Ingestion I had to change: Import Statements, Configuration and connection, Target Path, Data Type Conversion, Query compatibility,
General naming and references, Connection Handling.
For the Configuration I had to change: Constants, Class Names, Method for Database File, Configuration Key, Descriptions.
For the Connection I had to change: Classes, Class documentation, File Name, Import Statement, Connection Method, Isolation Level.

How has this been tested?

I've made a test program that first relied on the 'auto create feature' of the plugin. But after several errors I realized
that probably the auto create function wasn't functioning as expected.
So now the test doesn't rely on this function and instead doesn't create the table in advance, disables auto create, checks if the table is missing
and makes sure the ingestion logic remains.

What type of change are you making?

This is a new feature.
Now the users can make use of the DuckDB database from the list of database plugins.

[DeltaMichael]

Overall, the change looks ok. There are a few things you should do before merging:

1. Rebase your branch to main. Right now you're submitting 22 commits. Ideally, it should be ~1.

git pull origin main --rebase

2. Remove all the unnecessary files checked into version control, e.g. .db files
3. Change your commit message to use our commit template https://github.com/vmware/versatile-data-kit/blob/main/support/git-commit-template.txt
4. Add a description to the PR (usually, it's fine to just copy the commit message if you're using the template)
5. Address all comments

[antoniivanov]

Please remove also default_path.duckdb and temp.duckdb.

Normally, source code files are what you'd store in Git.
Auto-generated files, build artifacts or temporary files are not meant to be tracked in git. They are by-product of the code you write.

This enable us to keep the Git repository clean, organized, and efficient, adhering to best practices for source code management

[Maximiliaan72]

Overall, the change looks ok. There are a few things you should do before merging:

1. Rebase your branch to main. Right now you're submitting 22 commits. Ideally, it should be ~1.

git pull origin main --rebase

2. Remove all the unnecessary files checked into version control, e.g. .db files
3. Change your commit message to use our commit template https://github.com/vmware/versatile-data-kit/blob/main/support/git-commit-template.txt
4. Add a description to the PR (usually, it's fine to just copy the commit message if you're using the template)
5. Address all comments

[antoniivanov]

Looks good to me. Thanks for the contribution!