CI: Test Pyarrow Less
- [ ] closes #xxxx (Replace xxxx with the Github issue number)
- [ ] [Tests added and passed](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#writing-tests) if fixing a bug or adding a new feature
- [ ] All [code checks passed](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#pre-commit).
- [ ] Added an entry in the latest `doc/source/whatsnew/vX.X.X.rst` file if fixing a bug or adding a new feature.

CI has been really clogged w/ 2-3hr queue times.

Cut down on number of builds by only testing Pyarrow on one python version(if behavior is different based on Python version, that is pyarrow's problem). 

If compat continues to be an issue in the future, I would suggest that pyarrow test a "pandas-dev" build, similar to our numpydev builds. I have added one of these builds to fastparquet in the past, and it seems to be effective as there haven't been any recent issues with new fastparquet versions breaking CI IIRC.
This pull request is stale because it has been open for thirty days with no activity. Please [update](https://pandas.pydata.org/pandas-docs/stable/development/contributing.html#updating-your-pull-request) and respond to this comment if you're still interested in working on this.