PYR1-1556 Fix call-sql bigint arg overflow

[sifbiri]

Purpose

call-sql narrowed every integer argument to a 32-bit int before binding it, so a value
past about 2.1 billion (an epoch-millisecond timestamp, for example) threw an integer-overflow
error before it ever reached Postgres, even when the target column was a bigint.

It now narrows an integer only when it fits in 32 bits and leaves larger values as 64-bit longs,
which bind to bigint parameters correctly. In-range values are untouched, so existing callers
behave exactly as before. The same guard covers the double-to-float narrowing, which had the
matching overflow on very large doubles.

Adds unit tests for the coercion and for the call-sql wiring.