[persist] Upgrade arrow to fix a minor source roundtripping issue

[bkirwi]

Upgrading to pick up this upstream arrow fix: apache/arrow-rs#6953

Motivation

https://github.com/MaterializeInc/database-issues/issues/9318

Tips for reviewer

There were a couple minor API changes to adapt to as well, due to the upgrade, which explains most of the diff. (The largest is that chrono added a new method to a trait, shadowing our own method - I've adapted the code to use the upstream version instead.)

I've committed the proptest failure, though note that it's still hard to reproduce even so... the bug only appears when two floats hash to the same bucket in a hash table, which is cot common. I could only repro the original bug after several hours of cargo stress; so while I'm pretty confident this is the fix, it's hard to prove with testing.

Checklist

• This PR has adequate test coverage / QA involvement has been duly considered. (trigger-ci for additional test/nightly runs)
• This PR has an associated up-to-date design doc, is a design doc (template), or is sufficiently small to not require a design.
• If this PR evolves an existing $T ⇔ Proto$T mapping (possibly in a backwards-incompatible way), then it is tagged with a T-proto label.
• If this PR will require changes to cloud orchestration or tests, there is a companion cloud PR to account for those changes that is tagged with the release-blocker label (example).
• If this PR includes major user-facing behavior changes, I have pinged the relevant PM to schedule a changelog post.

[bkirwi]

Nightly run: https://buildkite.com/materialize/nightly/builds/12214

The only failure seems to already exist on main.