Avoid JDBC table to be set as transactional table

Found following issues in downstream integration.
1) JDBC tables created in some deployment environment were set as transactional tables by default. This caused catalogd failed to load the metadata for JDBC tables. We have to explicitly set table properties with "transactional=false" for JDBC tables.
2) FileSystemUtil.copyFileFromUriToLocal() function wrote log message only for IOException. We should write log message for all types of exceptions so that we can captures errors which caused failures to load JDBC drivers.
3) The operations on JDBC table are processed only on coordinator. The
processed rows should be estimated as 0 for DataSourceScanNode by planner so that coordinator-only query plans are generated for simple queries on JDBC tables and queries could be executed without invoking executor nodes.