Dialog box instead of fail / stack trace when plugin doesn't load

[cholmes]

The new installation code should hopefully make it rare for a duckdb import to fail, but it'd be good to have a better dialog when that happens. The init code should have an example of how to do a 'try' around the import, and then if it fails we should be able to load a dialog to inform the user it didn't work. I'm 90% sure this should work, but if it doesn't maybe there's another nice way to not just show a stack trace in the plugin dialog when the duckdb import fails.

It'd be also good in this code to check for DuckDB's that are below 1.1.0. Things sorta work when this happens, as it's a geospatially compatible parquet file that gets written out - it just won't have CRS information, but it will render in QGIS.