Add jdbc_tracing configuration option to control Snowflake JDBC driver logging

[kentoyoshida]

Summary

This PR adds a new jdbc_tracing configuration option that allows users to control the verbosity of Snowflake JDBC driver logs. This enhancement provides better debugging capabilities and allows users to reduce log noise in production environments.

Changes Made

• Configuration Option: Added jdbc_tracing parameter with default value "INFO"
• Valid Values: OFF, SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST, ALL
• Implementation: The option is passed directly to the Snowflake JDBC driver via the "tracing" property
• Documentation: Updated README.md with comprehensive description of the new parameter

Why This Is Useful

• Debugging: Developers can increase logging verbosity (e.g., FINE, FINER, FINEST) to troubleshoot connection issues, query performance, or other JDBC-related problems
• Production Optimization: Users can reduce log verbosity (e.g., WARNING, SEVERE) to minimize log output in production environments
• Flexibility: Provides granular control over JDBC driver logging without requiring code changes

Technical Details

The configuration is implemented by setting the tracing property on the JDBC connection properties, which is a standard Snowflake JDBC driver feature. The default value "INFO" maintains backward compatibility with existing behavior.

Test Plan

• Verify the configuration option is properly parsed and applied to JDBC connections
• Test with different logging levels (OFF, INFO, FINE, ALL) to confirm they affect log output appropriately
• Ensure backward compatibility by testing without the new parameter (should default to "INFO")
• Validate that invalid values are handled gracefully by the JDBC driver
• Test in both development and production-like environments to verify log behavior

🤖 Generated with Claude Code

[r-uehara0219]

LGTM