Bump booking/screens/signupinfo prod images; fix dev booking auth key

[scriptcoded]

Summary

Prod image version bumps for three already-deployed services, plus a dev config fix for booking.

Prod image bumps

• j26-booking 0.2.0 → 1.0.0 (app + migrate images, in lockstep — new-version migrations run via the init container on sync)
• j26-screens 0.1.0 → 1.0.0
• j26-signupinfo 0.1.0 → 1.0.1

Dev config fix (j26-booking)

• Replace the unused JWKS_URL key with OPEN_ID_CONFIGURATION_URL (the key the app actually reads). Dev was silently ignoring its auth config and falling back to the code default; dev and prod ConfigMaps now differ only by the auth URL host.

Notes

• The 1.0.0 / 1.0.1 image tags must exist in GHCR before merge, or pods will ImagePullBackOff (these apps pin explicit tags and are excluded from the image updater).
• screens has no ConfigMap/secrets/DB — zero prod config risk. signupinfo runs on an empty ConfigMap reusing dev Scoutnet KV keys.

🤖 Generated with Claude Code

[hakan-persson]

✅ Verified merge-ready (infra) — record

• All 4 image tags exist & pullable — j26-booking:1.0.0, j26-booking-migrate:1.0.0, j26-screens:1.0.0, j26-signupinfo:1.0.1 (cluster pull-tested). No ImagePullBackOff risk.
• Dev booking auth fix correct + isolated — JWKS_URL→OPEN_ID_CONFIGURATION_URL is the key the app actually reads. Does not leak to prod: prod booking is self-contained and already sets its own OPEN_ID_CONFIGURATION_URL (app.jamboree.se). Dev now matches prod's pattern.
• Booking migrations safe against the populated prod DB — the 4 new migrations (0.2.0→1.0.0) are additive on their up side (CREATE TABLE / ADD COLUMN); the DROPs are only in the down rollback halves. Existing data (12 tables) untouched.
• screens / signupinfo — trivial image bumps, no config/DB risk.

prod-review label auto-applied (dev-base file touched) → dev-only, prod isolated.

One watch item: the booking bump runs real schema migrations against the live prod DB. Additive/safe, but it's the one change with any risk — the migrate initContainer will be watched on merge to confirm clean completion.