support EXTRACT on intervals and durations

[nrc]

Which issue does this PR close?

Closes #6327.
Closes #7097

What changes are included in this PR?

Support extract/date_part by passing through requests to Arrow (where functionality was added in apache/arrow-rs#6071 and apache/arrow-rs#6246). There were also two changes required to the seconds helper function:

• If the number of nanoseconds overflows a 32 bit integer, (e.g., a DayTime interval of 5 seconds), then querying the nanoseconds returns null. However, it is reasonable to return a number of seconds in this case. However, if there is a non-round number of seconds, this will give an inaccurate answer, e.g., 5.1 seconds will get returned as 5, but I'm not sure how to solve this - returning null for round numbers of seconds seems bad. We could fall back to milliseconds, but that complicates the code, is still imperfect, and has less predictable results. I also had a question about how I did this (REVIEW comment in the code).
• The number of seconds was previously counted twice in cases where seconds are reflected in the number of nanoseconds.

A change which would fix both these issues (and I assume is an invariant which previously held) would be to not include whole seconds when returning nanoseconds. However, I think that breaks compat with Postgres.

Are these changes tested?

Yes, sqllogictests. The tests are not exhaustive because these features are properly tested in Arrow.

Are there any user-facing changes?

Users can use extract or date_part with intervals and durations.

[alamb]

Thanks @nrc -- this is looking really close to me.

I think we should reasses the null handling (I left a suggestion) as well as some additional testing but otherwise this is ready to go 🚀

[nrc]

Null handling and tests addressed. It took a tiny bit more code to make epoch work.

@alamb ready for re-review, thanks!

[alamb]

Looks great -- thank you @nrc and @samuelcolvin and @alexmojaki

[alamb]

👍