feat: network audio into the QSO recorder, and a Yaesu that stays on its VFO

An Icom reached over the LAN streams its receive audio through the Icom
protocol, and Windows sees no sound card for it at all — the audio settings
could only offer the PC's own microphone, so "From radio" had nothing right to
point at and the QSO recorder had nothing to record. The recorder now accepts a
PUSHED source: the decoded stream goes to the speakers and to the recorder
alike, with no virtual cable to set up. Which source it uses follows the CAT
backend, and it is restarted only when that answer changes, so an ordinary
settings save never cuts a recording in half.

OmniRig no longer sends SetSimplexMode to a Yaesu when tuning. It is a silent
no-op on some — an FT-891 logged OK on every spot click while FreqA never
moved — and actively harmful on others. From an FT-2000 log, one QSY:

	Vfo="AB"(0x80)  Split=0x10000 (off)   the operator's state
	Vfo="BA"(0x100) Split=0x8000  (ON)    after SetSimplexMode

The rig-agnostic "receive and transmit HERE, simplex" call turned split on and
moved reception to VFO B. OpsLog then displayed B — reading the radio correctly,
after having moved it itself. Icom is untouched: there the call is the
authoritative one and the direct write is unreliable.

Also:
  - the NEW county badge shows in the entry form itself, inside the field,
    where the operator is deciding whether to call.
  - the basemap buttons clear the zoom controls; Light sat a few pixels from
    the minus button and was being clicked by mistake.
  - French cluster status: DÉJÀ CTC reads DÉJÀ QSO.

frontend/src/App.tsx

@@ -5214,9 +5214,21 @@ export default function App() {
   };
   const geoDetailRow = (
     <div className="flex gap-4 items-end">
-      <div className="flex flex-col flex-1 min-w-0"><Label className="mb-1 h-3.5">{t('field.cnty')}</Label>
-        <Input value={details.cnty ?? ''}
+      {/* The badge sits INSIDE the field: this row is already tight, and a
+          county name is short enough to leave room at its right. It answers the
+          question at the moment the operator is deciding whether to call — the
+          same answer the Info tab gives, one tab away from where they are. */}
+      <div className="flex flex-col flex-1 min-w-0 relative"><Label className="mb-1 h-3.5">{t('field.cnty')}</Label>
+        <Input value={details.cnty ?? ''} className={cn(entryNewCounty && 'pr-12')}
           onChange={(e) => setDetails((d) => ({ ...d, cnty: e.target.value }))} />
+        {entryNewCounty && (
+          <span
+            title={t('detp.newCountyTip')}
+            className="absolute right-1.5 bottom-1.5 rounded px-1.5 py-0.5 text-[10px] font-bold tracking-wide bg-success text-success-foreground pointer-events-none"
+          >
+            {t('detp.newCounty')}
+          </span>
+        )}
       </div>
       <div className="flex flex-col w-[64px] shrink-0"><Label className="mb-1 h-3.5">{t('field.cqz')}</Label>
         <Input value={details.cqz ?? ''} className="font-mono"