Improve Add Database Connection dialog for SQLite, DuckDB, BigQuery, and Snowflake

[eirikbakke]

The "Add Database Connection" dialog supports various kinds of database-specific connection fields (host, port, database name etc.) These are automatically substituted into the JDBC driver specific JDBC URL.

This PR adds support for a "File" field, which will be shown if the user is using the JDBC drivers for SQLite or DuckDB. There is a "Browse" button that can be used to pick the file from a file browser. Furthermore, the username and password fields are hidden for these drivers, which are known not to require this kind of authentication.

For SQLite and DuckDB, there's a warning if the selected file is not of the right kind. (Useful because SQLite files do not have any kind of standardized file extension.)

For comparison, this is what the Add Database Connection dialog looked like before, for SQLite:

(There are some proprietary JDBC drivers for SQLite that do allow a password to be used for encryption, but in this rare case the user could use a connection property to pass this information instead.)

[eirikbakke]

The NewConnectionPanel uses the NetBeans Matisse Form Builder, by the way. The way it works is that the form contains every possible field available, and then individual fields are shown or hidden depending on what fields are used in the JDBC URL template string.

Here is the full dialog as it appears in the form builder:

To insert the "File" field I ended up hand-editing the ".form" file, reloading it in the form builder, making some adjustments, and then saving it again together with freshly generated initComponents() code. So the final "form" file committed here is generated by Matisse, not hand-edited by me.

[eirikbakke]

I added another commit which recognizes Snowflake JDBC URLs, just since we're already making enhancements to this piece of code.

[eirikbakke]

I squashed the previous review edits, and also added a separate commit which recognizes Google BigQuery JDBC URLs.

[mbien]

@eirikbakke could you rebase this PR? We might be able to squeeze this in.

[eirikbakke]

@eirikbakke could you rebase this PR? We might be able to squeeze this in.

Sure, done! Do you prefer a single squashed commit, or keep the three commits separate as they currently are?

Thanks!

[matthiasblaesing]

I see a small problem with h2 (the file part of the URL is not a full path) and nitpick regarding the JdbcUrl constructor.

[mbien]

Do you prefer a single squashed commit, or keep the three commits separate as they currently are?

I would probably squash it in this case, but do what you prefer.

[eirikbakke]

Thanks for review suggestions; I pushed a commit which incorporates them (will squash all commits into one before merging).

I also fixed two flaky tests in the same module. ("Fixed" by essentially calling Thread.sleep... a bit ugly, but there was already a convention for doing so in the same test file.)

[matthiasblaesing]

Thank you. Looks sane to me.

[mbien]

this looks ready other than needing squash and rebase.

[eirikbakke]

Thanks for reviewing! Merged!