viewer: render the queries section for synthetic runs

The synthetic renderer never read D.queries, so a campaign that swept
queries published all its cells and showed none of them.

Give it the section: a profile picker, per-op latency at the lowest
concurrency, p99 and throughput across the sweep, the setup rows each leg
records, and the read-path target table. The three figures are the same
grid the pubnet renderer already drew, so they move to a shared helper
both call rather than being written twice; the section gates off cleanly
for a run without queries, as the cold and variance sections do.

The target table judges a cell by its worst unit, so several units can be
over inside one cell. Reporting only the worst hid that: this run has
four breached cells but five profile-cells over the line. The cell now
flags the others with "+N more" and the verdict carries both counts, so a
hand count of a run's breaches reconciles with the table.

Author: marwen-abid