Add "presets" fields to module generation and execution benchmark configs

[pzread]

As we start adding large models to the benchmark suites, the single build target iree-benchmark-suites is not fine-grind enough to build what needs to be run and waste space and time to build unrelated large models.

Right now we have benchmark presets to control which ones to run and use tags on benchmark config to map benchmarks to benchmark presets. We can do this more easily by simply having a preset field on the benchmark configs. This also makes benchmark definitions clearly present which presets they belong to.

We can then also split the build targets of benchmark suites according to the presets. Initially we might have the build targets:

• iree-benchmark-suites-x86_64
• iree-benchmark-suites-cuda
• iree-benchmark-suites-vulkan-nvidia
• iree-benchmark-suites-android-cpu
• iree-benchmark-suites-android-gpu
• iree-benchmark-suites-x86_64-large
• iree-benchmark-suites-cuda-large

And for compilation benchmarks:

• iree-benchmark-suites-comp-stats
• iree-benchmark-suites-comp-stats-large

Then the meta build targets:

• iree-benchmark-suites-default: for default benchmarks
• iree-benchmark-suites-large: for large benchmarks