perf(lotw): stop asking for the QSL details by default

A tester compared LogHX's two download options on the same account: two minutes
for the confirmations, twenty for the confirmations with QSO details. OpsLog was
always sending qso_qsldetail=yes — LogHX's slow option — which is the whole of
the wait people were reporting.

Marking a confirmation needs call, date, band and mode; the detail adds the QSL
date and the station's grid, state and county. Now a choice, off by default, and
forced on when the download is also ADDING the QSOs it cannot find — the one
case where those fields have no other source.

frontend/src/lib/i18n.tsx

@@ -130,6 +130,8 @@ const en: Dict = {
   'icmp.scopeNoStream': 'This radio does not send its scope over CI-V — its own screen still works.',
   'gen.miles': 'Distances in miles', 'gen.milesHint': '(instead of kilometres)',
   'qslm.qrzTitle': 'Open this callsign on QRZ.com',
+  'qslm.lotwDetail': 'QSL details',
+  'qslm.lotwDetailTitle': 'Ask LoTW for the QSL date and the station details (grid, state, county) as well as the confirmation. LoTW takes about ten times longer to build that report — two minutes against twenty on the same account — and marking a confirmation needs none of it. Forced on when adding the QSOs not found, which have no other source for those fields.',
   'qslm.lotwAllCalls': 'All my callsigns',
   'qslm.lotwAllCallsTitle': "Download the confirmations of every callsign on the LoTW account, not just this profile's. A QSO made as F4BPO/P or TM2Q is confirmed at LoTW but never reaches an F4BPO profile without this.",
   'awp.filterSlotsNotCfmd': 'Slots to confirm', 'awp.slotGap': 'slots to confirm',
@@ -626,6 +628,8 @@ const fr: Dict = {
   'icmp.scopeNoStream': "Cette radio n'envoie pas son scope en CI-V — son propre écran fonctionne toujours.",
   'gen.miles': 'Distances en miles', 'gen.milesHint': '(au lieu des kilomètres)',
   'qslm.qrzTitle': 'Ouvrir cet indicatif sur QRZ.com',
+  'qslm.lotwDetail': 'Détails QSL',
+  'qslm.lotwDetailTitle': "Demander à LoTW la date du QSL et les détails de la station (locator, état, comté) en plus de la confirmation. LoTW met environ dix fois plus longtemps à construire ce rapport — deux minutes contre vingt sur le même compte — et marquer une confirmation n'en a pas besoin. Forcé quand on ajoute les QSO absents, qui n'ont pas d'autre source pour ces champs.",
   'qslm.lotwAllCalls': 'Tous mes indicatifs',
   'qslm.lotwAllCallsTitle': "Télécharger les confirmations de tous les indicatifs du compte LoTW, pas seulement celui du profil. Un QSO fait en F4BPO/P ou TM2Q est confirmé chez LoTW mais n'atteint jamais un profil F4BPO sans cette option.",
   'awp.filterSlotsNotCfmd': 'Slots à confirmer', 'awp.slotGap': 'slots à confirmer',