fix(bqjdbc): Log exception messages - part 3

[Neenu1995]

b/505826451

• Enhanced Error Logging: Updated catch blocks and direct exception throws across all files to ensure that when a severe error occurs, the specific exception and its message are logged.
• Logged Thrown Exceptions: In catch blocks where a new exception type is thrown (wrapping the original cause), we now log the new exception to make it clear what the application will see.
• Used Exception Messages: Updated the logs to use the message from the exception instance rather than hardcoded strings, ensuring more accurate context in the logs.
• Added Loggers: Added loggers to utility classes that previously couldn't log errors.

[gemini-code-assist]

Code Review

This pull request standardizes exception handling and logging across the BigQuery JDBC driver by ensuring that exceptions are logged at the severe level before being thrown. It introduces loggers to several utility classes and refactors catch blocks to provide more descriptive error messages. Review feedback suggests restoring lost context, specifically the 'catalogParam' variable, in BigQueryDatabaseMetaData and recommends using a static final logger in PooledConnectionDataSource to align with standard practices.

[logachev]

When we get Mdc working, can this LOG be a part of the exception? At least for exceptions that we own they could log sever errors, so we'll never forget to log it.