Keep the strict scenarios in step with main's photos and satellite groups

Main's flight photos ask Planespotters for every tracked aircraft, which
the strict network policy counted as a violation; the harness now answers
those lookups with no photos, as the other QA scripts already do. Main
also reads five more TLE groups (resource, weather, planet, SAR and
science): the satellite fixture serves them, and the space switch expects
all twelve groups and derives its catalog sizes from the fixture.

src/bench/satelliteFixture.js

@@ -28,6 +28,11 @@ const GROUPS = {
   galileo: [42000, 30, 56, 1.7047, 'QA GALILEO'],
   geo: [45000, 32, 0.1, 1.0027, 'QA GEO'],
   starlink: [50000, 6000, 53, 15.2, 'QA STARLINK'],
+  resource: [60000, 12, 98.2, 14.6, 'QA RESOURCE'],
+  weather: [61000, 8, 98.7, 14.1, 'QA WEATHER'],
+  planet: [62000, 24, 97.5, 15.1, 'QA PLANET'],
+  sar: [63000, 6, 97.9, 15.0, 'QA SAR'],
+  science: [64000, 6, 28.5, 15.1, 'QA SCIENCE'],
 };
 export const SATELLITE_FIXTURE_EPOCH = W1_FROZEN_MS;
 export function satelliteFixture(group) {

src/bench/satelliteFixture.test.mjs

@@ -16,6 +16,11 @@ test('satellite fixture has distinct, valid SGP4 catalogs including LEO, MEO and
     galileo: 30,
     geo: 32,
     starlink: 6000,
+    resource: 12,
+    weather: 8,
+    planet: 24,
+    sar: 6,
+    science: 6,
   };
   for (const [group, count] of Object.entries(counts)) {
     const lines = satelliteFixture(group).trim().split('\n');