fix: Do not import SQLException in the SQL handler

The agent was encountering a NoClassDefFoundError for java.sql.SQLException
in some environments due to class loading issues.

- Removed direct import of java.sql.SQLException.
- Changed catch blocks in getDbName methods to catch Throwable instead of
  SQLException to broaden exception handling and prevent crashes when
  SQLException is not directly available.

Author: dividedmind

agent/src/main/java/com/appland/appmap/process/hooks/SqlQuery.java

@@ -2,7 +2,6 @@
 
 import java.sql.Connection;
 import java.sql.DatabaseMetaData;
-import java.sql.SQLException;
 import java.sql.Statement;
 
 import com.appland.appmap.output.v1.Event;
@@ -55,7 +54,7 @@ private static String getDbName(Connection c) {
       }
 
       dbname = metadata.getDatabaseProductName();
-    } catch (SQLException e) {
+    } catch (Throwable e) {
       Logger.println("WARNING, failed to get database name");
       e.printStackTrace(System.err);
     }
@@ -74,7 +73,7 @@ private static String getDbName(Statement s) {
       }
 
       dbname = getDbName(s.getConnection());
-    } catch (SQLException e) {
+    } catch (Throwable e) {
       Logger.println("WARNING, failed to get statement's connection");
       e.printStackTrace(System.err);
     }