feat(grantrecs): grant-history join + daily opportunity projection (#1218)

[paulalbert1]

Funding matcher: grant-history join + daily opportunity projection (#1218)

Two related follow-ups from docs/funding-matcher-redesign-handoff.md, bundled under the #1218 umbrella. Review only — do not merge.

Step 3 — grant-history join (app)

Extends the reverse matcher ("rank researchers for this opportunity") with each scholar's grant/degree history:

• deriveGrantSignals() (pure, unit-tested) → esiEligible / yearsSinceDegree / fundingStatus, attached post-ranking.
  • fundingStatus uses the canonical isFundingActive (12-month NCE grace), so it agrees with the profile's "Active funding" badge — not a bespoke endDate >= now.
  • esiEligible dates from the terminal research/clinical degree (PhD/MD/…), not the most recent credential, so a later MPH/cert doesn't falsely reset the ESI clock.
• ESI clause in researcherBlurb; funding-status filter dropdown; funding + "Also in their Grants for me" row badges; two new CSV columns.
• Cross-ref (opportunitiesInTopMatches): a cheap MySQL-only topic-affinity top-N over the open-opportunity corpus — gated to the same status/deadline the forward matcher uses, so a closed/past-due opp (reachable via the unfiltered browse list) can never over-claim "in their Grants for me." Validated against the real forward matcher in scripts/funding-crossref-compare.ts: 100% top-10 agreement, past-due guard clean.

Step 2 — daily opportunity projection (cdk)

etl:dynamodb (DynamoDB→MySQL opportunity projection) is a nightly step but sits after etl:ed, which #443 blocks — so the nightly aborts before reaching it and newly-published opportunities 404 until re-projected by hand.

• Adds a standalone daily etl:dynamodb schedule (06:30 UTC) in Sps-Etl, mirroring the curation-backup pattern (task → retry → catch → state machine → rule → cadence alarm).
• Creation-gated on a new opportunityProjectionScheduleEnabled flag: staging true, prod false (prod creates no resources until the corpus is published / Staging Session B: populate data + build search index #443 lands and the nightly reaches the step again, at which point the stopgap retires).

Review & verification

• Step 3 went through a multi-agent adversarial review; the 3 confirmed issues (funding-active divergence, ESI terminal-degree, cross-ref over-claim) are fixed in this PR and re-verified.
• App: affected unit suites green (grant-signal/ESI/funding/CSV coverage added); tsc + eslint clean.
• cdk: etl-stack 130 tests green; staging snapshot updated; prod synth creates zero projection resources (creation-gated).
• Cross-ref comparison + field population verified end-to-end against the local DB + OpenSearch.

Deploy (operator, gated — not in this PR)

• Step 2: cdk deploy Sps-Etl-staging to activate the daily schedule.
• Step 3: app image roll carries the code.
• Staging visual verify (handoff Step 1) and prod rollout (Step 4) remain follow-ups.

Accepted residuals

• Cross-ref skips per-scholar stage/US eligibility flags (status/deadline gate removes the dominant false-positive source) — documented in code.
• Comparison numbers are from the local 12-opp corpus; re-run the harness on staging's 653 to confirm at scale.