feat(sat): PstRotator can point the antenna too

It handles azimuth and elevation, and a great many stations already run
it in front of a controller OpsLog has never heard of. For those,
OpsLog talking to the controller itself would be a second program
fighting PstRotator over the same cable — so it hands over the bearing
instead, and lets PstRotator turn the mast.

Both kinds sit behind one small interface, chosen in Settings. Neither is
more correct than the other: the right one is whichever the station
already has working.

The 450° overlap is deliberately NOT applied on the PstRotator path.
PstRotator knows which machine is on the other end and does its own; two
programs each deciding to go the long way round is exactly how an antenna
unwinds in the middle of a pass.

Position queries are asked at most every three seconds rather than on
every tick. A PstRotator query binds a socket and waits up to a second
and a half, and many setups answer nothing at all — so one silence is
enough and it stops asking, reporting the commanded position instead and
saying that is what it is.

frontend/wailsjs/go/models.ts

@@ -4136,6 +4136,8 @@ export namespace main {
 	    grid: string;
 	    alt_m: number;
 	    rot_on: boolean;
+	    rot_type: string;
+	    rot_pst_port: number;
 	    rot_transport: string;
 	    rot_host: string;
 	    rot_port: number;
@@ -4159,6 +4161,8 @@ export namespace main {
 	        this.grid = source["grid"];
 	        this.alt_m = source["alt_m"];
 	        this.rot_on = source["rot_on"];
+	        this.rot_type = source["rot_type"];
+	        this.rot_pst_port = source["rot_pst_port"];
 	        this.rot_transport = source["rot_transport"];
 	        this.rot_host = source["rot_host"];
 	        this.rot_port = source["rot_port"];