Add multiple aliases for a Benchmark

[epompeii]

A Benchmark can now be identified by its name, slug, or UUID: #629

This helps align Benchmarks with the other dimensions (Branch, Testbed, and Measure).

It would be great to be able to track multiple aliases for a Benchmark over time with an array of exact match strings.

[
  "current_benchmark::name",
  "old_benchmark::name",
]

The name field could then become a "display name" similar to #366.
The current name would just be added as the first entry in the match array.

[Louisvranderick]

This looks like something I’d be interested in helping implement.

One thing I’m not sure is decided yet: where should the alias list live in the schema? For example:

• Separate table (e.g. one row per alias, FK to benchmark, with something like UNIQUE(project_id, alias) so two benchmarks can’t claim the same string), or
• A column on benchmark (e.g. JSON array of strings), with uniqueness enforced in application code (or triggers).

That choice would tell us how get_or_create resolves BenchmarkNameId::Name and how we handle updates. Happy to follow whatever direction maintainers prefer.

[epompeii]

@Louisvranderick thank you for the interest!

I think the first option you described, a benchmark_alias table with a UNIQUE(project_id, alias) constraint would be the way to go.

With that said, I'm currently working on getting v0.6 out the door. Smaller changes like adding an adapter (#601 / #728) are fine to fold in. However, a change this large would be on hold for the next couple of weeks. You're welcome to start working on it now. I just wanted to give you a heads up that I would wait to merge it in.

[Louisvranderick]

Hello! I opened a PR for this here: #742
Totally understand this may wait until after the v0.6 push but Im sharing early so you can review whenever timing works.