Fix pyarrow test

[mvanschellebeeck]

This fixes #4448

The last successful pyarrow test on master ran here on ubuntu-20.04 and the most recent failure ran here on ubuntu-22.04

ubuntu-latest is starting a transition from 20.04 to 22.04 and it looks like it just hit - see https://github.blog/changelog/2022-11-09-github-actions-ubuntu-latest-workflows-will-use-ubuntu-22-04/

[jackwener]

LGTM, Thanks @mvanschellebeeck
Fixing this version is a good choice, using a rolling upgrade version can easily cause dependency problem.

[ursabot]

Benchmark runs are scheduled for baseline = 8e0556b and contender = d9e58db. d9e58db is a master commit associated with this PR. Results will be available as each benchmark for each run completes.
Conbench compare runs links:
[Skipped ⚠️ Benchmarking of arrow-datafusion-commits is not supported on ec2-t3-xlarge-us-east-2] ec2-t3-xlarge-us-east-2
[Skipped ⚠️ Benchmarking of arrow-datafusion-commits is not supported on test-mac-arm] test-mac-arm
[Skipped ⚠️ Benchmarking of arrow-datafusion-commits is not supported on ursa-i9-9960x] ursa-i9-9960x
[Skipped ⚠️ Benchmarking of arrow-datafusion-commits is not supported on ursa-thinkcentre-m75q] ursa-thinkcentre-m75q
Buildkite builds:
Supported benchmarks:
ec2-t3-xlarge-us-east-2: Supported benchmark langs: Python, R. Runs only benchmarks with cloud = True
test-mac-arm: Supported benchmark langs: C++, Python, R
ursa-i9-9960x: Supported benchmark langs: Python, R, JavaScript
ursa-thinkcentre-m75q: Supported benchmark langs: C++, Java

[alamb]

Thank you @mvanschellebeeck !