CI: Bump pandas-gbq to one that doesn't pin pyarrow

[lithomas1]

• closes #xxxx (Replace xxxx with the GitHub issue number)
• Tests added and passed if fixing a bug or adding a new feature
• All code checks passed.
• Added type annotations to new arguments/methods/functions.
• Added an entry in the latest doc/source/whatsnew/vX.X.X.rst file if fixing a bug or adding a new feature.

[mroeschke]

Might be worth bumping the min version to https://github.com/googleapis/python-bigquery-pandas/releases/tag/v0.18.1 so users also don't get bit by pyarrow being pinned

[lithomas1]

Ugh 0.18.1 isn't on conda-forge.

Is it fine to just go directly to 0.19.x?

[mroeschke]

Ugh 0.18.1 isn't on conda-forge.

Is it fine to just go directly to 0.19.x?

Yeah that should be fine

[mroeschke]

A few more places need bumping otherwise looks good

[lithomas1]

Not entirely making sense of the error, but looks like there is a conflict between pyarrow dependencies
(aws-sdk-cpp) and google-bigquery dependencies(grpcio) fighting over openssl 1 and openssl 3.

I think what needs to happen is that we need to bump pyarrow from 7 to something newer.

PDEP-10 stops this from happening for 2.1, but maybe we can bump as soon as 2.2?
There seems to be no support plan in that PDEP, stopping us from bumping pyarrow as we please.

cc @jorisvandenbossche (this relates to the issue with pyarrow effectively being pinned on CI)

[github-actions]

This pull request is stale because it has been open for thirty days with no activity. Please update and respond to this comment if you're still interested in working on this.

[mroeschke]

Going to close to clear the queue for now

[mroeschke]

I think I may have tackled this in #55524?

[lithomas1]

Nice, thanks Matt.