feat(cluster): quiet the worked spots, light up the empty slots

Two options that change what the eye is pulled towards, both applying to the
cluster list AND the band map.

Mute worked before: a spot that brings nothing new loses its colour and its
badges. It stays in the list - the operator asked for less noise, not less
information. "Brings nothing new" reuses the dimming rule the cluster list
already had rather than inventing a second notion of done, so it keeps obeying
the same-slot option and the digital-mode grouping for free. A new-band or
new-slot status is NOT muted: having worked that callsign once on another band
says nothing about the band in front of you.

Highlight unworked in this slot: colours any callsign not yet worked on this
band and this mode, whatever the entity says. For an operator filling slots a
common entity on a fresh band+mode is the whole point, and the entity-level
status flatly calls it worked. It reuses the existing new-slot status, so no new
colour, no new legend, no new badge - both panels already knew how to draw it.

WorkedSlot is computed independently of the same-slot preference: it is what
this option reads, and it must not change meaning because a different option was
toggled. The slot index is now built when either option needs it, and the status
cache is keyed on both so a toggle invalidates it.

The rules live in one module used by both panels. Marker colours already taught
us what happens when the two derive the same thing separately.

frontend/wailsjs/go/models.ts

@@ -3012,6 +3012,7 @@ export namespace main {
 	    new_pota: boolean;
 	    new_pfx: boolean;
 	    pfx?: string;
+	    worked_slot: boolean;
 	
 	    static createFrom(source: any = {}) {
 	        return new SpotStatus(source);
@@ -3030,6 +3031,7 @@ export namespace main {
 	        this.new_pota = source["new_pota"];
 	        this.new_pfx = source["new_pfx"];
 	        this.pfx = source["pfx"];
+	        this.worked_slot = source["worked_slot"];
 	    }
 	}
 	export class StartupStatus {