GH-50078: [C++][ORC] Avoid signed overflow when converting timestamps

[jmestwa-coder]

Rationale for this change

A far-future ORC timestamp (after ~2262) makes AppendTimestampBatch in cpp/src/arrow/adapters/orc/util.cc overflow int64 nanoseconds in seconds * kOneSecondNanos + nanos. Reducing the multiply under -fsanitize=signed-integer-overflow:

runtime error: signed integer overflow:
  10000000000 * 1000000000 cannot be represented in type 'int64_t'

What changes are included in this PR?

Detect the overflow with MultiplyWithOverflow/AddWithOverflow and return Status::Invalid for out-of-range values instead of computing the product with undefined behavior. Null slots are skipped.

Are these changes tested?

Verified the offending expression with a standalone -fsanitize=signed-integer-overflow reproducer and confirmed the patched path returns an error rather than overflowing.

Are there any user-facing changes?

No.

• GitHub Issue: [C++][ORC] Signed integer overflow when converting far-future timestamps #50078

[kou]

• Could you open an issue for non MINOR change? See https://github.com/apache/arrow/blob/main/CONTRIBUTING.md#Minor-Fixes for details.
• Could you use our PR template instead of removing it entirely?

[wgtmac]

I agree with @kou. Changes like this require an issue. The change itself looks good.

[jmestwa-coder]

Opened #50078 for this and retitled the PR to reference it. Also restored the PR template. Thanks both.

[github-actions]

⚠️ GitHub issue #50078 has been automatically assigned in GitHub to PR creator.

[wgtmac]

Thanks for updating it! Is it possible to add a test case?

[jmestwa-coder]

Added one in adapter_test.cc (TimestampOutOfRangeIsRejected) - it feeds a far-future ORC timestamp (10000000000s, ~year 2286) through AppendBatch and asserts it returns Invalid instead of overflowing.