Update date_bin to support Time32 and Time64 data types

[Omega359]

Which issue does this PR close?

Part of #19025

Rationale for this change

Expand support for binning time data types.

What changes are included in this PR?

Code, tests.

Are these changes tested?

Yes, slt tests.

Are there any user-facing changes?

No.

[martin-g]

Consider adding the following constants:

const NANOS_PER_MILLI: i64 = 1_000_000;
const NANOS_PER_SEC: i64 = 1_000_000_000;
const NANOS_PER_MICRO: i64 = 1_000;

[Omega359]

Thanks for the review @martin-g. I've implemented your review feedback - sorry for the numerous bugs in that initial version :(

[Jefffrey]

Could you explain why for time we require the expression & origin arguments to have the same granularity in terms of time units, whereas for timestamps above we seem to always have origin as Nanoseconds regardless of the expression granularity?

[Omega359]

It didn't occur to me essentially :/

[Omega359]

I took a look at this and it's a bit more than just the timeunit - it's the type. For time32 there is just two timeunits supported - Second and Millisecond. For Time64 it's Microsecond and Nanosecond.

Supporting a mix of those I think would be unnecessary. Forcing a single type (Time64(Nanosecond)) might work but I don't see it as beneficial really. Are you of a different opinion?

[Jefffrey]

I was more thinking of trying to simplify the signature (which looks a bit gnarly) and potentially the implementation too. In terms of actual functionality it should be fine.

[Jefffrey]

Thanks @Omega359 & @martin-g