Ability to run just a single benchmark on the CI

[Akirathan]

Closes #12322

Pull Request Description

Important Notes

Running

env ENSO_BUILD_BENCH_NAME=Warning ./run --skip-version-check backend benchmark runtime

locally invokes just sbt engine-benchmarks/benchOnly Warning, as expected.

Running

./run --skip-version-check backend benchmark runtime

locally invokes all the benchmarks via sbt engine-benchmarks/bench. This is the old behavior.

Checklist

Please ensure that the following checklist has been satisfied before submitting the PR:

• The documentation has been updated, if necessary.
• Screenshots/screencasts have been attached, if there are any visual changes. For interactive or animated visual changes, a screencast is preferred.
• All code follows the
  Scala,
  Java,
  TypeScript,
  and
  Rust
  style guides. In case you are using a language not listed above, follow the Rust style guide.
• Unit tests have been written where possible.
• If meaningful changes were made to logic or tests affecting Enso Cloud integration in the libraries,
  or the Snowflake database integration, a run of the Extra Tests has been scheduled.
  • If applicable, it is suggested to paste a link to a successful run of the Extra Tests.

[Akirathan]

We first have to merge this PR and then test the manual scheduling. The changes to the Engine benchmark and Standard Libraries benchmark will be reflected once this PR is merged.

[Akirathan]

On https://github.com/enso-org/enso/actions/runs/13417305101/job/37481181145 I have scheduled a single benchmark run with bench name of org.enso.interpreter.bench.benchmarks.semantic.VectorBenchmarks.averageOverSlice. And it works only benchmarks that contains this string as name were run.

GitHub

Benchmark Engine · enso-org/enso@560e9a5

Enso Analytics is a self-service data prep and analysis platform designed for data teams. - Benchmark Engine · 560e9a5