fix: the status bar named the settings database, not the logbook

Spotted by the author: on SQLite the database chip showed a.dbPath — the
settings/profile database — under a tooltip reading "Local SQLite logbook".

Those became two separate files when the logbook was split out, so an operator
checking where their QSOs live, or which file to copy before a trip, was pointed
at the wrong one. MySQL was already right.

It now resolves the logbook the same way connectLogbook does: the active
profile's own file if it names one, then the default logbook.db, and the settings
db only in the case where it genuinely doubles as the logbook.

Also moves the 4O3A mark beside its menu label instead of the far edge of the
row, as asked.

frontend/src/components/SettingsModal.tsx

@@ -216,7 +216,7 @@ function VendorMark({ vendor }: { vendor: 'o3a' }) {
 	// match the surrounding menu at any theme or zoom.
 	const lens = [3.2, 5.2, 7.4, 9.5, 7.4, 5.2, 3.2]; // half-heights, tallest in the middle
 	return (
-		<span className="ml-auto flex shrink-0 items-center gap-[1px] text-[10px] font-bold leading-none opacity-80" title="4O3A Signature">
+		<span className="ml-1.5 flex shrink-0 items-center gap-[1px] text-[10px] font-bold leading-none opacity-80" title="4O3A Signature">
 			<span>4</span>
 			<svg viewBox="0 0 26 22" className="h-[13px] w-[15px]" aria-hidden="true">
 				{lens.map((ry, i) => (