GH-34256: [Dev] Update release scripts with main as new default branch

[lafiona]

Rationale for this change

This is a follow up task after switching the apache/arrow default branch name from master to main. Usages of master were evaluated to determine whether they can be switched over to main.

What changes are included in this PR?

Only once instance of usage of master was changed. The other usages depend on master being used as the default branch in external repositories.

This is a summary of my investigation:

post-04-ruby.sh

• Modified URL to use HEAD instead of master to refer to the most updated version of the code.

post-12-msys2.sh

• The usages of master is referring to the default branch of msys2/MINGW-packages
• Since the default branch used by the repo is still master this will be kept until they swap over.

post-13-homebrew.sh

• The usage of master in this file is similar to that of post-12-msys2.sh. It is referring to the default branch of the homebrew/homebrew-core repository, which is still using master as the default branch.

post-14-vcpkg.sh

• The usage of master in this file is similar to that of post-12-msys2.sh. It is referring to the default branch of the microsoft/vcpkg repository, which is still using master as the default branch.

post-15-conan.sh

• The usage of master in this file is similar to that of post-12-msys2.sh. It is referring to the default branch of the conan-io/conan-center-index repository, which is still using master as the default branch.

Are these changes tested?

I verified the change in post-04-ruby.sh by navigating to the new URL and confirming the contents are the same as the existing URL. Additionally, existing release CI tests will run as part of this pull request.

Are there any user-facing changes?

No, users nor users of the development tools should see a difference in behavior from this change.

• Closes: [Release] Update release scripts with main as new default branch #34256

[github-actions]

• Closes: [Release] Update release scripts with main as new default branch #34256

[github-actions]

⚠️ GitHub issue #34256 has no components, please add labels for components.

[github-actions]

⚠️ GitHub issue #34256 has no components, please add labels for components.

[lafiona]

I received an email requesting me to set the component for this pull request, but it seems like I might not have permission to do so. Can a reviewer set the component to Dev?

[kou]

+1

I received an email requesting me to set the component for this pull request

It requested for the associated issue not this pull request.

but it seems like I might not have permission to do so. Can a reviewer set the component to Dev?

It seems that @raulcd did it: #34256 (comment)

[ursabot]

Benchmark runs are scheduled for baseline = 5a7d89c and contender = 3b9ea6d. 3b9ea6d is a master commit associated with this PR. Results will be available as each benchmark for each run completes.
Conbench compare runs links:
[Finished ⬇️0.0% ⬆️0.0%] ec2-t3-xlarge-us-east-2
[Failed ⬇️0.37% ⬆️0.0%] test-mac-arm
[Finished ⬇️0.0% ⬆️0.0%] ursa-i9-9960x
[Finished ⬇️0.1% ⬆️0.0%] ursa-thinkcentre-m75q
Buildkite builds:
[Finished] 3b9ea6dd ec2-t3-xlarge-us-east-2
[Finished] 3b9ea6dd test-mac-arm
[Finished] 3b9ea6dd ursa-i9-9960x
[Finished] 3b9ea6dd ursa-thinkcentre-m75q
[Finished] 5a7d89cf ec2-t3-xlarge-us-east-2
[Failed] 5a7d89cf test-mac-arm
[Finished] 5a7d89cf ursa-i9-9960x
[Finished] 5a7d89cf ursa-thinkcentre-m75q
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