Get WAE ready: the score split, the Cabrillo layouts and the QTC list

The score summary now splits the way N1MM's does. `ContestLog` keeps a tally
per band, and per kind of row where the contest has kinds, and the score window
reads those instead of adding the rows up itself. Three things were wrong with
the old sum:

- The band rows counted a multiplier as one whatever the band. WAE weights it
  by band — `ScoreRow.AddContact` adds four on 3.5, three on 7 and two on 14,
  21 and 28 — so the band rows did not add up to the total.
- The band rows counted contacts left out of the claimed score.
- There was no split by kind. `CWAE.LogInfo` and `ScoreClass.Description` give
  WAE a `Q/QTC` column and a row per band and kind, so contacts, traffic sent
  and traffic received are read apart.

The Cabrillo writer now pads the record name to seven characters, which is what
`ConvertCabrilloStructStdToString` does and why: `X-QSO:` is six characters and
a space, so every record name puts the frequency in the same column. Nonemm
wrote five, and the `X-QSO:` lines added last commit did not line up with the
rest.

WAE's own layouts follow `CWAE.CabrilloString`: three spaces after the sent
serial rather than the one every other column gets, and the transmitter column
only for a multi-operator entry.

`QtcTraffic.ToSend` no longer offers a contact marked as a dupe, which is what
`DBSupport.QTCRecordsetCount` leaves out with `Trim(ContactType) = ''`.

Checked by running the program against a WAE SSB log of six contacts and a
series of ten received: the band rows read 4, 3, 2 and 2 and add up to the 11
in the total row.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015NZkFxHde1iifAQemFTHxf

src/Nonemm.Formats/Cabrillo/CabrilloWriter.cs

@@ -62,6 +62,8 @@ public sealed class CabrilloWriter
         return text.ToString();
     }
 
+    private const int TagWidth = 7;
+
     public string QsoLine(Qso qso)
     {
         CabrilloExchange exchange = contest.CabrilloExchange(qso, me, entry);
@@ -82,13 +84,17 @@ public sealed class CabrilloWriter
     /// A contact the operator has excluded from the claimed score is still
     /// written, under `X-QSO:` rather than `QSO:`. That is what N1MM writes,
     /// and the sponsors read it as a contact the entrant is not claiming.
+    ///
+    /// The tag is padded to seven so that the columns after it line up whichever
+    /// tag the row carries. That is the width N1MM pads it to, and `X-QSO:` is
+    /// why: six characters and one space.
     private string RecordName(Qso qso)
     {
         if (!contest.IsContact(qso))
         {
-            return "QTC: ";
+            return "QTC:".PadRight(TagWidth);
         }
-        return qso.IsClaimed ? "QSO: " : "X-QSO: ";
+        return (qso.IsClaimed ? "QSO:" : "X-QSO:").PadRight(TagWidth);
     }
 
     /// Every column is the width the sponsor asks for and one space, and a