fix(deps): allow pyarrow v8

[parthea]

No description provided.

[bnaul]

Sorry to hijack but what's the motivation for always capping the version at whatever is released today? It's a bit frustrating as a user to not be able to use a recently released package because some other dependency has an overly restrictive range of allowed versions. In the opposite case, the user is always free to add say pyarrow<9 to their own requirements.txt if they want, but with the current setup I'm pretty much stuck on waiting on another version bump to get everything working.

Appreciate the quick fix here, just wondering if maybe the current system is more hassle than it's worth.

[meredithslota]

@bnaul The reason that we use this approach is because a new major version of a dependency can break users who do not explicitly restrict them via requirements.txt. We know it is best practice to have a requirements.txt file but not all users do that. In addition, it may take time for our code or samples to be re-written/fixed in order to have compatibility with a new major version, and we'd prefer to err on the side of not accidentally breaking folks. We try to update as soon as possible. Thanks!