Seed default History/Membership schedules per managed club

[Sootopolis]

Depends on

• First-class managed_club marker (server-scoped, forward-compatible to per-user) #101 — first-class managed_club marker (the non-leaky source of "my clubs").

What

Extend boot-seeding (from #45) to ensure default History and Membership JobSchedule rows per managed club only — never for all known clubs (heavy History crawls against incidental scouted/opponent clubs would blow up the DB).

• Enumerate managed clubs via First-class managed_club marker (server-scoped, forward-compatible to per-user) #101 (ManagedClub.selectClubIds).
• For each, idempotently seed a History and a Membership schedule scoped to that club_id. Per-club rows have a non-null club_id, so INSERT ... ON CONFLICT (kind, club_id) DO NOTHING works directly (unlike the global NULL-club_id rows in Bootstrap default JobSchedule rows for server-internal kinds at first boot #45, which needed a WHERE NOT EXISTS guard).
• Cadence/enable from the same scheduler.defaults HOCON block introduced in Bootstrap default JobSchedule rows for server-internal kinds at first boot #45 — add history / membership entries.
• The existing per-club scheduler dispatch already handles History/Membership (JobScheduler.runSchedule → requireClubSlug → HistoryApp.discover(slug) / MembershipApp.reconcile(slug)); no all-clubs History path is needed.

Resolved (in #105)

• Seed timing: boot-only, in ServerTables.ensureTables — mirrors Bootstrap default JobSchedule rows for server-internal kinds at first boot #45's seed model; ManagedClubApp.mark stays untouched. A club marked managed while the server is up gets its schedules on the next boot.
• Defaults: History 24h, Membership 24h, both enabled; new scheduler.defaults.history / .membership HOCON blocks with ${?SCHEDULER_HISTORY_*} / ${?SCHEDULER_MEMBERSHIP_*} overrides.
• Resurrection / don't-clobber: matches Bootstrap default JobSchedule rows for server-internal kinds at first boot #45 exactly — ON CONFLICT DO NOTHING leaves an existing (incl. edited/disabled) row untouched, and re-seeds a user-deleted row on the next boot. Off-switch is enabled = false on the live row, or unmanage the club.

Out of scope (follow-up)

• All-clubs History (explicitly rejected in Bootstrap default JobSchedule rows for server-internal kinds at first boot #45).
• The managed-club concept itself (First-class managed_club marker (server-scoped, forward-compatible to per-user) #101).
• Unmanaging a club does NOT delete its existing per-club job_schedule rows (job_schedule.club_id FKs club, not managed_club), so they keep firing. Should be a follow-up: delete/disable per-club schedules on ManagedClub.delete.

Relationship

• Split out of Bootstrap default JobSchedule rows for server-internal kinds at first boot #45; depends on First-class managed_club marker (server-scoped, forward-compatible to per-user) #101; under epic Epic: CLI v0 (Phase 1) #40.

---

Resolved by #105 (squash-merge 42a0559d81922afa7538a514fe80ab4d901edba3). Main CI green.

[Sootopolis]

Context: #45 shipped (globals-only) in #103 / 31d8874. Per-club History/Membership seeding lands here, on top of #101.

[Sootopolis]

Dependency #101 is merged (#104 / 9f79396). ManagedClub.selectClubIds (managed, tombstone-excluded) is the non-leaky source to seed per-managed-club History/Membership from. Unblocked.