ARROW-18120: [Release][Dev] Run binaries/wheels verifications in 05-binary-upload.sh

[kou]

[kou]

@raulcd What do you think about this?

[github-actions[bot]]

https://issues.apache.org/jira/browse/ARROW-18120

[github-actions[bot]]

:warning: Ticket has not been started in JIRA, please click 'Start Progress'.

[kou]

The only think I am not sure is that this comment also triggers the verify-rc-binaries-jars-* but the jars are supposed to be uploaded on the 06-java-upload.sh.

Good catch! Then, how about running 06-java-upload.sh before 05-binary-upload.sh? Or how about creating 07-binary-verify.sh?

[kou]

Or how about creating 07-binary-verify.sh?

I chose this.

[ursabot]

Benchmark runs are scheduled for baseline = 917f70b8b52aaefa99f55fcd80a7645d33de8550 and contender = 6697826746c1c871bb673a94299d3a235f20ff2e. 6697826746c1c871bb673a94299d3a235f20ff2e is a master commit associated with this PR. Results will be available as each benchmark for each run completes. Conbench compare runs links: [Finished :arrow_down:0.0% :arrow_up:0.0%] ec2-t3-xlarge-us-east-2 [Failed :arrow_down:0.34% :arrow_up:0.0%] test-mac-arm [Failed :arrow_down:0.0% :arrow_up:0.0%] ursa-i9-9960x [Finished :arrow_down:0.24% :arrow_up:0.0%] ursa-thinkcentre-m75q Buildkite builds: [Finished] 66978267 ec2-t3-xlarge-us-east-2 [Failed] 66978267 test-mac-arm [Failed] 66978267 ursa-i9-9960x [Finished] 66978267 ursa-thinkcentre-m75q [Finished] 917f70b8 ec2-t3-xlarge-us-east-2 [Finished] 917f70b8 test-mac-arm [Failed] 917f70b8 ursa-i9-9960x [Finished] 917f70b8 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