bulk building platorm names: please adjust or explain why I'm confused

[Greg Troxel <gdt%lexort.com@localhost>]

We are increasingly using tools that parse build output, and I'm finding
some things harder than I think they need to be.

At

  https://releng.netbsd.org/bulktracker/www/firefox-esr

one can see results for firefox-esr (which is basically that it builds
on only 3 platforms).

The platform strings seem mostly sensible: "OS version/arch", except

  - There are several that are "Description: ".  That seems about the
    sources (and the reason to run it), not about the plattform.

  - "Rocky Linux" probably should be "Rocky_Linux" for ease of parsing.


Under branch, I expect to see

  - 2024Q2 (as a standard abbreviation for pkgsrc-2024Q2, presumably but
    that's fine)

  - HEAD

and that's about it, for the most part.

I realize mnx is operating a soft fork, and that there could reasonably
be "upstream-HEAD" when the build is of the imported copy of pkgsrc that
intends to bit-for-bit match pkgsrc HEAD, and something else when it's
mnx's working version -- perhaps mnx-HEAD.

There are strings like:

  - el9-trunk-x86_64
  - evbarm7-9.0-2024Q2
  - trunk-x86_64

These have platforms in them to varying degrees, but that isn't about
the sources.

Whether it is because of variant naming, or a BT issue, the checkbox
"Show latest build result for each platform" isn't doing what it should,
or perhaps the checkbox that are "show head and most recent branch only"
is missing.

It could be that we should have some kind of comment field for one-off
bulk test runs, and that BT should show it.  But it also seems like
those tests have code beyond the branch and the branch token could give
that hint.

If you think I'm confused here, please feel free to explain :-)
If not, and you're running a build, I'd appreciate it if you could
regularize the branch/platform fields.