Restore the type squares in the results grids

[MDA2AV]

#1017 removed the infrastructure tier and took the other four type colours with it. All five lived on a single line:

.tsq-flagship{...} .tsq-emerging{...} .tsq-experimental{...}
.tsq-engine{...} .tsq-infrastructure{...}

so deleting "the infrastructure badge rule" deleted the line. Every other removal in that commit was correctly scoped -- the filter pill, the tooltip, the abbreviation, the localStorage whitelist, the isScored branch and .b-infrastructure were all infrastructure-only. This one wasn't, because the line was shared.

.tsq kept its width, height and border-radius but lost every background, so each square rendered as a 10x10 transparent box. Both grid renderers still emit class="tsq tsq-<type>", so nothing was wrong with the markup -- there was simply no colour to paint. The yellow tuned ring kept showing because it is a ::after with its own background, which is why the squares looked like they vanished from beside an otherwise intact marker.

Restores the four surviving colours at their original values, unchanged and still matching the .b-* badge and filter-pill palette (flagship #2e9e6a, emerging #3b73c4, experimental #d98e2b, engine #cb5f51). One rule per line now, so removing a tier can't silently take the others again.

Verified in headless Chrome against the real data files, on this branch and on main for comparison:

                          main            this branch

flagship + emerging 51/51 transparent 0/51, correct colours
engine 26/26 transparent 0/26, rgb(203,95,81)
experimental 2/2 transparent 0/2, rgb(217,142,43)

Checked in both grid renderers (composite table and profile grid) and in dark mode; the tuned ring still renders.

Description

---

PR Commands — comment on this PR to trigger (requires collaborator approval):

Command	Description
/benchmark -f <framework>	Run all benchmark tests
/benchmark -f <framework> -t <test>	Run a specific test
/benchmark -f <framework> --save	Run and save results (updates leaderboard on merge)

Always specify -f <framework>. Results are automatically compared against the current leaderboard.

---

Run benchmarks locally

You can validate and benchmark your framework locally with the lite script — no CPU pinning, fixed connection counts, all load generators run in Docker.

./scripts/validate.sh <framework>
./scripts/benchmark-lite.sh <framework> baseline
./scripts/benchmark-lite.sh --load-threads 4 <framework>

Requirements: Docker Engine on Linux. Load generators (gcannon, h2load, h2load-h3, wrk, ghz) are built as self-contained Docker images on first run.