fix(sat): LilacSat-2 keeps its FM transponder

Shipped with nothing but an APRS digipeater on 144.390, which is not what
anybody works that satellite on. The FM transponder — 144.350 up, 437.200 down —
was dropped by the generator, correctly by its own rule: SatNOGS marks that
transmitter inactive.

And SatNOGS is not wrong. LilacSat-2's transponder is switched on to an
announced schedule rather than left running, and from a database a scheduled
transponder looks exactly like a dead one. The judgement belongs to whoever
reads the diff, not to the filter.

So the transponder goes back in, labelled "(scheduled)" the way PO-101 already
is, and the satellite takes its OSCAR name, LO-90, with LILACSAT-2 and CAS-3H as
aliases so the element feeds still meet it.

The generator now reports what it refused on that ground and kept nothing else
for — one line per satellite, phrased as a question. Reviving every inactive
transponder would fill the list with birds that answer nothing; saying nothing
is how this one shipped wrong. There is no third option that a filter can decide
on its own.

Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>

internal/sat/birds.json

@@ -390,15 +390,25 @@
     ]
   },
   {
-    "name": "LILACSAT-2",
+    "name": "LO-90",
     "norad": 40908,
     "transponders": [
+      {
+        "label": "FM voice transponder (scheduled)",
+        "mode": "FM",
+        "down_lo": 437200000,
+        "up_lo": 144350000
+      },
       {
         "label": "APRS Digipeater",
         "mode": "DATA",
         "down_lo": 144390000,
         "up_lo": 144390000
       }
+    ],
+    "aliases": [
+      "LILACSAT-2",
+      "CAS-3H"
     ]
   },
   {