GH-50819: [Release] Increase YUM verification timeout

[erichanwang]

Rationale for this change

The arm64 YUM release-verification job can exceed its 30-minute limit when the EPEL mirror is slow. Issue #50819 reports repeated timeouts during the 25.0.1 verification, including a package download taking about 15 minutes at roughly 23 kB/s. Increasing the shared matrix job timeout gives the verification enough time to complete under this documented slow-mirror condition.

What changes are included in this PR?

• Increase yum in .github/workflows/verify_rc.yml from timeout-minutes: 30 to timeout-minutes: 60.
• The job is a shared matrix for ubuntu-latest and ubuntu-24.04-arm, so the timeout change applies to both architectures while keeping the workflow structure unchanged.

Are these changes tested?

The workflow remains valid YAML, and git diff --check passes. This is a CI configuration-only change; no runtime test is applicable.

Are there any user-facing changes?

No direct user-facing API changes. Release verification is less likely to fail due to transient slow package mirrors.

• GitHub Issue: [Release] Binary verification YUM job for arm64 is timing out for 25.0.1 #50819

[github-actions]

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

[github-actions]

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

[kou]

+1

[conbench-apache-arrow]

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

There was 1 benchmark result with an error:

• Commit Run on amd64-m5-4xlarge-linux at 2026-08-13 07:22:58Z
  • tpch (R) with engine=arrow, format=parquet, language=R, memory_map=False, query_id=TPCH-15, scale_factor=10

There were no benchmark performance regressions. 🎉

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

[conbench-apache-arrow]

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

There was 1 benchmark result with an error:

• Commit Run on amd64-m5-4xlarge-linux at 2026-08-13 07:22:58Z
  • tpch (R) with engine=arrow, format=parquet, language=R, memory_map=False, query_id=TPCH-15, scale_factor=10

There were no benchmark performance regressions. 🎉

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