unpin pyarrow for windows

[mattip]

Why are these changes needed?

Toward fixing #38300

PR #29993 added a local ray fix for issue apache/arrow#26685, but at the time windows failed the tests with pyarrow7. In issue #38300 the suggested fix was

• release the pin
• add a version check when serializing a pyarrow dataset
• Handle any remaining behavior gap related to _register_arrow_data_serializer(), and include an environment variable to override the Pyarrow version check

Checks

• I've signed off every commit(by using the -s flag, i.e., git commit -s) in this PR.
• I've run scripts/format.sh to lint the changes in this PR.
• I've included any doc changes needed for https://docs.ray.io/en/master/.
  • I've added any new APIs to the API Reference. For example, if I added a
    method in Tune, I've added it in doc/source/tune/api/ under the
    corresponding .rst file.
• I've made sure the tests are passing. Note that there might be a few flaky tests, see the recent failures at https://flakey-tests.ray.io/
• Testing Strategy
  • Unit tests
  • Release tests
  • This PR is not tested :(

[mattip]

step 1: release the pin. Let's see what tests fail?

[mattip]

I also ran the test added in #29993 locally and it passed.

[mattip]

cc @anyscalesam

[mattip]

I think releasing the pin is enough to solve the issue.

[mattip]

I don't think the CI failure is related. It would be nice to get some eyes on this.

[edoakes]

CI failure is likely unrelated. Updating branch to re-run

[scottjlee]

Contents of PR LGTM - I triggered a postmerge test to see how things look on windows tests.
https://buildkite.com/ray-project/postmerge/builds/2689

[scottjlee]

LGTM, @c21 to approve and merge

[RocketRider]

Could we pick that for 2.9.2?

[tonyhoo]

When will this fix be released. It introduced installation issue for AutoGluon on Windows platform with Python 3.11