fix: SPLIT placed the transmitter on a stale VFO; share the meter widget

Reported on the FTDX10: listening on 14.244 with VFO B still holding 18.115 from
an earlier session, pressing SPLIT threw the transmitter onto another band. The
button only flipped the rig's split flag, and the other VFO is stale by nature —
the only transmit frequency that makes sense is one derived from where the
operator is listening NOW. SPLIT therefore places the TX VFO too: up 1 kHz on CW
and the data modes, up 5 kHz on phone, the offsets operators actually call. The
+1k / +5k buttons remain for anything else, and a test pins the mapping.

The panel also drew its own flat meters while the Flex and Icom consoles use the
shared LED-segment MeterBar. Two instrument styles in one application is just
inconsistency — it now uses the shared component, and the local one is gone.

And the three consoles are named alike: "Flex Console", "Icom Console", "Yaesu
Console", in the tabs and in the Main-view pane list, in both languages.

frontend/src/App.tsx

@@ -5371,9 +5371,9 @@ export default function App() {
                   </span>
                 </TabsTrigger>
               )}
-              {catState.backend === 'flex' && <TabsTrigger value="flex">FlexRadio</TabsTrigger>}
-              {catState.backend === 'icom' && <TabsTrigger value="icom">Icom</TabsTrigger>}
-              {catState.backend === 'yaesu' && <TabsTrigger value="yaesu">Yaesu</TabsTrigger>}
+              {catState.backend === 'flex' && <TabsTrigger value="flex">Flex Console</TabsTrigger>}
+              {catState.backend === 'icom' && <TabsTrigger value="icom">Icom Console</TabsTrigger>}
+              {catState.backend === 'yaesu' && <TabsTrigger value="yaesu">Yaesu Console</TabsTrigger>}
               {statsTabOpen && (
                 <TabsTrigger value="stats" className="gap-1.5">
                   {t('stats.tab')}