Right now the list of variants when doing a perf patch build is very overwhelming. To make it worse, the "normal" version of each variant ends up sorted in the middle of a bunch of specialized versions. We should take advantage of evergreen sorting them ASCIIbetically on display_name to bring some order to the chaos. On the main mongo evergreen, we use ! and * prefixes to mark highest and next highest priority groupings. This may not make sense on the perf configs if there aren't sufficiently common variants.

simon.eismann@mongodb.com made the following suggestion on slack:

We could change the naming scheme, so that the specialization of the variant comes first:

• PERF 1-Node ReplSet (Bonsai with Heuristic CE) ARM AWS 2023-11 --> [Bonsai with Heuristic CE] 1-Node ReplSet ARM AWS 2023-11
• PERF 1-Node ReplSet (Classic Query Engine) ARM AWS 2023-11 --> [Classic Query Engine] 1-Node ReplSet ARM AWS 2023-11
  This would group all the Bonsai variants and all the CQE variants together, which should be useful.

There was a concern that this would affect history, but because the database uses the more stable name rather than display_name, that shouldn't be a problem.