Consider benchmarks to baseline GC and perf

We probably don't need this for the `Corvus.Configuration.TestEnvironment` because it used only to run unit tests, so serious performance problems will only affect developers, who will be motivated to fix it. But there is one runtime aspect to this: the name provider. Either add benchmarks, or make a positive decision that we're not going to do that and update the IMM accordingly.

Start by inspecting the runtime name provider and the existing IMM referenced in the issue. Determine whether meaningful GC and performance benchmarks can be defined for that runtime path; done means either adding a reproducible benchmark baseline or recording and applying a clear decision not to benchmark in the IMM.

Written by the indexing model from the issue text.