fix: drop invalid Crustdata business emails and retry enrich

[skwowet]

Summary

Crustdata returns HTTP 400 and rejects the whole /person/enrich request when any business_emails value is not a valid business identifier (for example a government-domain address). That failed Temporal enrichMember for members with no LinkedIn and only those emails, even though other enrichment sources could still succeed.

Changes

• In getDataUsingWorkEmails, catch only 400 + invalid_request + Invalid business emails: ….
• Parse the comma-separated invalid list from the error message, drop those emails, and retry with whatever remains.
• Return null when nothing is left so the workflow caches a miss and continues. All other 400s still throw.

[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.

[Copilot]

Pull request overview

Handles Crustdata invalid-business-email responses while allowing enrichment to continue.

Changes:

• Parses rejected emails from specific 400 responses.
• Retries with valid remaining emails.
• Returns null when none remain.

Suppressed comments (1)

services/apps/members_enrichment_worker/src/sources/crustdata/service.ts:297

• This comment only restates the immediately following split/filter operation, contrary to the repository's no-narrative-comments convention. The code is self-explanatory without it.

        // The API returns all invalid emails as a comma-separated list in the error message.
        // Exclude them so valid emails can still be enriched on the next attempt.

---

💡 Configure MCP servers for context-aware, tailored reviews. Learn more in the docs.