fix(array): guard BinaryViewBuilder size checks

[fallintoplace]

What changed

BinaryViewBuilder now checks view value lengths as int before any narrowing conversion to int32. Both ReserveData and Append use the same size guard.

The regression test covers oversized ReserveData lengths and oversized byte slices without allocating multi-gigabyte buffers.

Why

The previous check converted lengths to int32 before comparison. Values larger than math.MaxInt32 could wrap negative and bypass the 2GB guard.

Validation

• go test ./arrow/array -run 'TestBinaryViewBuilderRejectsOversizedValues|TestBinaryViewStringRoundTrip'
• go test ./arrow/array
• go test ./arrow/...
• go test -tags assert ./arrow/array

[zeroshade]

if the concern is wrapping past the int32 max value, this should be explicitly int64(viewValueSizeLimit) instead of just int so that it is correct on 32-bit systems also.

[zeroshade]

Thanks — extracting checkBinaryViewValueSize(length int64) addresses my earlier note: the comparison is now done in int64 (length > int64(viewValueSizeLimit)), so the previous int32(length) truncation on 64-bit is gone and Append/ReserveData share one guard. TestBinaryViewBuilderRejectsOversizedValues (size-guard + ReserveData, the latter correctly skipped on 32-bit) passes locally. LGTM.

Heads-up: #895 reuses the binaryViewNoAllocAllocator helper this PR introduces, so this one should merge first.