fix: fix invalid version specification of pyarrow

[mamo3gr]

Make version specification of pyarrow fulfill PEP404.

• Make sure to open an issue as a bug/issue before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea
• Ensure the tests and linter pass
• Code coverage does not decrease (if any source code was changed)
• Appropriate docs were updated (if necessary)

Fixes #1402 🦕

[conventional-commit-lint-gcf]

🤖 I detect that the PR title and the commit message differ and there's only one commit. To use the PR title for the commit history, you can use Github's automerge feature with squashing, or use automerge label. Good luck human!

-- conventional-commit-lint bot
https://conventionalcommits.org/

[mamo3gr]

@aribray @chalmerlowe There seems to be something wrong with the build process. Could you tell me how to rerun kokoro in this PR and/or debug it on my local computer? I cherry-picked some commits from the main branch and they might solve the problem.

Many thanks for considering my request.

[chalmerlowe]

@mamo3gr

we have been doing some other changes in other PRs related to pyarrow, etc.
let me take a look at this PR and make sure everything lines up.

[chalmerlowe]

@mamo3gr @tswast

Looking at the the current file on main, it looks like pyarrow was moved out of the extras category at some point and was listed as a simple dependency: https://github.com/googleapis/python-bigquery/blob/main/setup.py

Am I missing something? Is this PR still relevant?

[tswast]

@chalmerlowe Note that this is targeting the v1 branch. We have intentionally kept that branch alive for potential support for high priority fixes. Up to us if this qualifies.