ARROW-14976: [Dev][Archery] Fail early if no benchmark found

[cyb70289]

If no benchmark matches the suite/benchmark filter, current benchmark
tool will build Arrow twice, run no benchmark, and fail with confusing
error message.

This patch is to fail after the first build when the benchmark tool
finds no benchmark to run.

[github-actions]

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

[github-actions]

⚠️ Ticket has not been started in JIRA, please click 'Start Progress'.

[kszucs]

@cyb70289 can we cover this change with a unittest in test_benchmarks.py?

[cyb70289]

@cyb70289 can we cover this change with a unittest in test_benchmarks.py?

@kszucs, not sure if there's simple way to test it.

Current workflow is to first build all the benchmarks, then scan *-benchmark files and select wanted binaries per suite_filter, then list benchmarks by running the binary xxx-benchmark --benchmark_list_tests and apply benchmark_filter to select wanted benchmarks. Only after that we can judge if the suite/benchmark filter is valid.

[ursabot]

Benchmark runs are scheduled for baseline = 9d200f5 and contender = f0110cf. f0110cf 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.45% ⬆️0.0%] ursa-i9-9960x
[Finished ⬇️0.49% ⬆️0.04%] ursa-thinkcentre-m75q
Supported benchmarks:
ec2-t3-xlarge-us-east-2: Supported benchmark langs: Python. Runs only benchmarks with cloud = True
ursa-i9-9960x: Supported benchmark langs: Python, R, JavaScript
ursa-thinkcentre-m75q: Supported benchmark langs: C++, Java