refactor: add neverReenrich support and clean up worker structure

[skwowet]

Note

Medium Risk
Touches enrichment selection criteria and cache invalidation semantics (including SQL query conditions), which can materially change which members/orgs get enriched and when. The remaining changes are mostly refactors/moves but could introduce runtime wiring issues if any imports/Temporal schedule IDs drift.

Overview
Adds neverReenrich support across member and organization enrichment sources: service/type contracts now allow cacheObsoleteAfterSeconds to be optional when neverReenrich is enabled, cache-obsolescence checks short-circuit when neverReenrich is true, and enrichment candidate queries (fetchMembersForEnrichment, fetchOrganizationsForEnrichment) treat such sources as enrich-once by only selecting entities with no existing cache row.

Refactors members_enrichment_worker structure by splitting LLM helpers into activities/llm.ts, consolidating member-related activities (including OpenSearch sync) into activities/member.ts and removing activities/syncEnrichedData.ts, routing workflows to import from the new activities barrel, and renaming/rewiring the top-level enrichment trigger workflow from getMembersToEnrich to triggerMembersEnrichment with schedules separated (new refreshMembersEnrichmentMaterializedViews schedule file). Also removes the onboarding script and its package scripts.

^{Written by Cursor Bugbot for commit 4710c1d. This will update automatically on new commits. Configure here.}

[github-actions]

⚠️ Jira Issue Key Missing

Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability.

Example:

• feat: add user authentication (CM-123)
• feat: add user authentication (IN-123)

Projects:

• CM: Community Data Platform
• IN: Insights

Please add a Jira issue key to your PR title.

[github-actions]

⚠️ Jira Issue Key Missing

Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability.

Example:

• feat: add user authentication (CM-123)
• feat: add user authentication (IN-123)

Projects:

• CM: Community Data Platform
• IN: Insights

Please add a Jira issue key to your PR title.

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

[github-actions]

⚠️ Jira Issue Key Missing

Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability.

Example:

• feat: add user authentication (CM-123)
• feat: add user authentication (IN-123)

Projects:

• CM: Community Data Platform
• IN: Insights

Please add a Jira issue key to your PR title.

[github-actions]

⚠️ Jira Issue Key Missing

Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability.

Example:

• feat: add user authentication (CM-123)
• feat: add user authentication (IN-123)

Projects:

• CM: Community Data Platform
• IN: Insights

Please add a Jira issue key to your PR title.

[github-actions]

⚠️ Jira Issue Key Missing

Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability.

Example:

• feat: add user authentication (CM-123)
• feat: add user authentication (IN-123)

Projects:

• CM: Community Data Platform
• IN: Insights

Please add a Jira issue key to your PR title.