improve Dremio destination

[rudolfix]

Following items are left or improving over #1026

1. • use SQL MERGE statement for merging (Add upsert merge strategy #1129 )
2. • add gcp and azure storage
3. • prevent NOT NULL in ALTER TABLE (Dremio ignores nullability)
4. • using a sentinel table for destinations that have no schemas/datasets actually makes sense. we do that for vector databases. we also support empty dataset names so tables are not prefixed (not sure it applies here after all)
5. • we can implement dremio adapter to expose all the partition/clustering/retention features (some are implemented but adapters let users to add the hints conveniently to the resources)
6. • Dremio recently fixed a bug that enables the use of the ADBC client [Python] Querying Dremio with the ADBC Flight SQL client apache/arrow-adbc#1559. We could therefore remove the pydremio.py file and cut over to ADBC. I don't think there is any rush on this.
7. • I'd like to test a wider selection of destination data source types in Dremio. We are somewhat hamstrung by the lack of CREATE SCHEMA support, which is why the CI tests run against a "NAS" (really local file system). I know that Dremio does support CREATE FOLDER sql statements for Nessie catalogs, so Nessie might be next logical thing to add to the testing pipelines as it should be possible to get all the tests passing against it. It might also be worth running a subset of the tests that don't require CREATE SCHEMA against a Hive Metastore data source.
8. • I can foresee that we may want to expose a "path_prefix" config option to build tables at arbitrarily nested levels in a folder structure.