Update for pyarrow 17

[rauerhans]

We need pyarrow 17 in one of our projects, because of other dependency constraints. However, we also need 3.3.0, because we are facing unstable database connections with this library's version < 3. So it'd be lovely to relax the dependency on Pyarrow < 17 to include the latest stable version of 17.

[arredond]

(copying over from the PR comments)

I see the fix here is to move to pyarrow<18.0 as the upper bound. Would you consider not adding an upper bound at all? Upper bounds really make dependency management much, much harder for complex projects.

Here's a nice discussion on the topic.

Also, I see this has already been a problem for other users in the past: #389 , #390 , #55