fix: handle date_bin negative subsecond and overflow cases

[kumarUjjawal]

Which issue does this PR close?

• Closes date_bin scalar & array paths have different error behaviours #22528

Rationale for this change

date_bin had a few edge cases that could return the wrong result, return an error only on array inputs, or panic/wrap when scaling timestamp and time values to nanoseconds.

What changes are included in this PR?

• Fix negative sub-second timestamp conversion before the epoch.
• Make scalar and array paths return NULL consistently for per-row binning errors.
• Use checked scaling when converting timestamp and time values to nanoseconds.
• Return an error for invalid shared origin values that overflow during scaling.
• Simplify duplicated stride and scale handling.

Are these changes tested?

Yes

Are there any user-facing changes?

No public API changes.