Delete all in-tree benchmark infrastructure code. (#18144)

See the related RFC:
https://groups.google.com/g/iree-discuss/c/n039Q0trkHk

Deleted components _directly_ related to benchmark infrastructure:
* Workflow files in `.github/workflows/`: benchmark triggering, e2e test
artifact generation, benchmark compilation stats, benchmark execution,
comment posting
* Benchmark configuration and series definitions (mix of Python scripts,
CMake generators, CMake files, etc.)
* Documentation relating to benchmarks on pull requests / using GitHub
Actions

Deleted components _indirectly_ related to benchmark infrastructure:
* Support scripts like
`build_tools/benchmarks/set_android_scaling_governor.sh` (could be
useful for developers, but doesn't need to live in-tree)
* `iree_run_module_test` (was used to test correctness for _some_
benchmark workloads but was not fully adopted)
* Build presets in `build_tools/cmake/` scripts (e.g. `test`,
`benchmark`, `benchmark-with-tracing`): too complex, trying to steer
away from build scripts and towards CMake presets or explicit workflows
without that indirection

Future cleanup possibilities:
* `build_all.yml` (no longer any references)
* Docker files: android, nvidia, nvidia-bleeding-edge

Closes #7795
Closes #8631
Closes #10599
Closes #10928
Closes #11703
Closes #11922
Closes #11953
Closes #14993
Closes #15452
Closes #16057
Closes #16157
Closes #16396
Closes #16431
Closes #17749

.github/CODEOWNERS

@@ -38,7 +38,6 @@
 
 # Infra Top-Level Directories
 /build_tools/ @ScottTodd
-/build_tools/benchmarks/ @antiagainst
 /build_tools/python_deploy/ @stellaraccident
 /build_tools/scripts/ @ScottTodd
 /build_tools/third_party/ @ScottTodd @stellaraccident