GH-40536: [CI]: Migrate remaining jobs away from self-hosted mac runners.

[assignUser]

Rationale for this change

CRAN no longer builds on 10.13 and gh provides M1 runners now.

What changes are included in this PR?

use m1 for verify-rc-binaries-wheels-macos-14-arm64:
and macos-11 for r-binary-packages

Are these changes tested?

crossbow

• GitHub Issue: [CI] Replace additional self-hosted runners from crossbow  #40536

[assignUser]

@github-actions crossbow submit verify-rc-binaries-wheels-macos-14-arm64 r-binary-packages

[github-actions]

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

[kou]

@github-actions crossbow submit verify-rc-binaries-wheels-macos-14-arm64 --param release=15.0.2 --param rc=3

[assignUser]

ugh, brew doesn't support macos 11 anymore so it tries to build sccache from source...

Warning: You are using macOS 11.
We (and Apple) do not provide support for this old version.
It is expected behaviour that some formulae will fail to build in this old version.
It is expected behaviour that Homebrew will be buggy and slow.
Do not create any issues about this on Homebrew's GitHub repositories.
Do not create any issues even if you think this message is unrelated.

Lets just bump to 12, 11 will be removed in Q2 anyway: actions/runner-images#9255

[github-actions]

Revision: 346c036

Submitted crossbow builds: ursacomputing/crossbow @ actions-1797eb513d

Task	Status
verify-rc-binaries-wheels-macos-14-arm64

[assignUser]

@github-actions crossbow submit r-binary-packages

[github-actions]

Revision: 661fa28

Submitted crossbow builds: ursacomputing/crossbow @ actions-52e3f3edc1

Task	Status
r-binary-packages

[kou]

verify-rc-binaries-wheels-macos-14-arm64 worked. I'll unify verify-rc/github.macos.{arm,amd}64.yml.

[kou]

@github-actions crossbow submit verify-rc--macos- --param release=15.0.2 --param rc=3

[kou]

@github-actions crossbow submit verify-rc--macos- --param release=15.0.2 --param rc=3

[github-actions]

Revision: 9a5ecad

Submitted crossbow builds: ursacomputing/crossbow @ actions-98b9c07bdc

Task	Status
verify-rc-binaries-wheels-macos-11-amd64
verify-rc-binaries-wheels-macos-12-amd64
verify-rc-binaries-wheels-macos-14-arm64
verify-rc-source-cpp-macos-amd64
verify-rc-source-cpp-macos-arm64
verify-rc-source-cpp-macos-conda-amd64
verify-rc-source-csharp-macos-amd64
verify-rc-source-csharp-macos-arm64
verify-rc-source-go-macos-amd64
verify-rc-source-go-macos-arm64
verify-rc-source-integration-macos-amd64
verify-rc-source-integration-macos-arm64
verify-rc-source-integration-macos-conda-amd64
verify-rc-source-java-macos-amd64
verify-rc-source-js-macos-amd64
verify-rc-source-js-macos-arm64
verify-rc-source-python-macos-amd64
verify-rc-source-python-macos-arm64
verify-rc-source-python-macos-conda-amd64
verify-rc-source-ruby-macos-amd64
verify-rc-source-ruby-macos-arm64

[kou]

verify-rc-source-cpp-macos-arm64 and verify-rc-source-cpp-macos-conda-amd64 failures will be passed on main because main has 5127ef0#diff-aa8c7db0f10c202b555dd103c54828afa0e8cbd781e87694b5ac4705beba2cdeR1068 .

[kou]

+1

[raulcd]

Thanks both @kou and @assignUser for the effort!

[conbench-apache-arrow]

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

There were no benchmark performance regressions. 🎉

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