chore(udp): name the service for the protocol, not for one program

"WSJT-X logged QSO (Logger32)" reads as Logger32-only, and it is not: the row
speaks the WSJT-X UDP interface, which several loggers listen on. An operator
running something else would have scrolled past a service that would have
worked for them.

Logger32 stays in the hint as the example it is — it is what this was built
against, and its additional sockets are where most people will point it — and
port 2250 stays as the default, a starting point rather than a rule.

frontend/src/components/UDPIntegrationsPanel.tsx

@@ -78,9 +78,11 @@ const SERVICE_TYPES: Array<{
     defaults: { port: 2333, destination_ip: '127.0.0.1' },
   },
   {
-    // The same ADIF, wrapped in the WSJT-X protocol. Logger32's extra UDP
-    // sockets (2250 / 2251 / 2252) listen on that interface and drop plain
-    // text without a word, which is why this cannot be the row above.
+    // Announces the QSO on the WSJT-X UDP interface instead of as plain text.
+    // Named for the protocol, not for one program: Logger32 is what it was
+    // built against, but anything listening on that interface takes it, and a
+    // label saying "Logger32" would have every other operator scroll past.
+    // 2250 is Logger32's first additional socket — a starting point, not a rule.
     id: 'wsjt_log',
     direction: 'outbound',
     label: 'udpp.svcWsjtLogLabel',