Fix verify_release.sh script to run rustfmt in each crate individually

[alamb]

Which issue does this PR close?

re

Rationale for this change

#2339 changes the release candidates so there is no workspace (Cargo.toml) any longer and thus cargo fmt fails when the verify_release_candidate.sh script is run.

What changes are included in this PR?

Run rustfmt for each of the crates individually -- as the tests were changed in #2339

Are there any user-facing changes?

No

[ursabot]

Benchmark runs are scheduled for baseline = 7ce6ba4 and contender = 68934f0. 68934f0 is a master commit associated with this PR. Results will be available as each benchmark for each run completes.
Conbench compare runs links:
[Skipped ⚠️ Benchmarking of arrow-rs-commits is not supported on ec2-t3-xlarge-us-east-2] ec2-t3-xlarge-us-east-2
[Skipped ⚠️ Benchmarking of arrow-rs-commits is not supported on test-mac-arm] test-mac-arm
[Skipped ⚠️ Benchmarking of arrow-rs-commits is not supported on ursa-i9-9960x] ursa-i9-9960x
[Skipped ⚠️ Benchmarking of arrow-rs-commits is not supported on ursa-thinkcentre-m75q] ursa-thinkcentre-m75q
Buildkite builds:
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