fix(bigquery-jdbc): normalize setTime from Calendar zone to JVM zone

[keshavdandeva]

b/565818805

Summary

Fixes PreparedStatement.setTime(..., Calendar) and CallableStatement.setTime(..., Calendar) applying the Calendar timezone offset in the wrong direction.

Problem

BigQueryTemporalUtility.convertTimeWithCalendar(Time, Calendar) shifts wall-clock time fields from the JVM default timezone into the target Calendar's timezone (the read-side direction used by CallableStatement.getTime(..., Calendar)). Calling it in setTime(..., Calendar) shifted the offset in the opposite direction before BigQueryParameterHandler formatted the Time in the JVM default timezone.

Changes

• Added BigQueryTemporalUtility.convertTimeToCalendar(Time, Calendar) (mirroring convertDateToCalendar) to extract local time fields in the provided Calendar's timezone and normalize them to 1970-01-01 in the JVM default timezone.
• Updated BigQueryPreparedStatement.setTime(int, Time, Calendar) and BigQueryCallableStatement.setTime(String, Time, Calendar) to call convertTimeToCalendar.
• Added unit tests in BigQueryTemporalUtilityTest, BigQueryPreparedStatementSettersTest, and BigQueryCallableStatementTest.

[gemini-code-assist]

Code Review

This pull request introduces a new utility method convertTimeToCalendar in BigQueryTemporalUtility to convert and normalize java.sql.Time parameters using a target Calendar's timezone, and updates BigQueryCallableStatement and BigQueryPreparedStatement to use it. Unit tests have also been expanded to cover these cross-timezone conversions. The feedback suggests refactoring convertTimeToCalendar to use legacy Calendar manipulation instead of java.time APIs to ensure proper handling of Daylight Saving Time (DST).