GH-49757: [Release][CI] export SSL_CERT_FILE to bypass incompatibility with OpenSSL on RHEL-8

[raulcd]

Rationale for this change

The binary wheel verification is taking around 50 minutes locally, It is timing out on CI. After some investigation, see the issue, this is related to: https://bugzilla.redhat.com/show_bug.cgi?id=1053882

What changes are included in this PR?

Export SSL_CERT_FILE before running the verification on almalinux-verify-rc job.

Are these changes tested?

Yes, I tested this locally due to the binary verification not easily being tested on CI.

Locally executed the following which is exactly the same that the biniary verification CI job exercises:

$ time ALMALINUX=8 archery docker run -e TEST_DEFAULT=0 -e TEST_WHEELS=1 -e VERBOSE=1 -e VERIFY_RC=0 -e VERIFY_VERSION=24.0.0 -e GH_TOKEN=$GH_TOKEN almalinux-verify-rc

It took previously ~50 minutes to complete (got clearly stuck on test_fs.py), it currently takes 7 minutes:

+ TEST_SUCCESS=yes
+ echo 'Release candidate 24.0.0-RC0 looks good!'
Release candidate 24.0.0-RC0 looks good!
+ exit 0
+ cleanup
+ '[' yes = yes ']'
+ rm -fr /tmp/arrow-24.0.0.CTLOf

real	7m4.906s
user	0m3.660s
sys	0m1.626s

Are there any user-facing changes?

No

• GitHub Issue: [Python][Release] test_s3_options takes 11 minutes to complete on wheels verification for almalinux #49757

[github-actions]

⚠️ GitHub issue #49757 has been automatically assigned in GitHub to PR creator.

[kou]

+1

[kou]

+1

[conbench-apache-arrow]

After merging your PR, Conbench analyzed the 3 benchmarking runs that have been run so far on merge-commit f092b91.

There were no benchmark performance regressions. 🎉

The full Conbench report has more details. It also includes information about 2 possible false positives for unstable benchmarks that are known to sometimes produce them.