fix: serialize member enrichment org savepoints

[skwowet]

Summary

Fixes a savepoint "... " does not exist failure in member enrichment.

The issue came from running multiple organization writes in parallel inside one DB transaction. Each write could create nested savepoints, and one rollback could invalidate another in-flight savepoint.

This PR makes those organization writes run sequentially and syncs after the DB transaction commits.

---

Note

Medium Risk
Changes transaction execution by making organization upserts sequential and moving syncOrganization outside the member update transaction, which could affect throughput and timing but reduces risk of transactional savepoint conflicts.

Overview
Prevents member enrichment failures caused by parallel organization writes inside a single DB transaction by serializing findOrCreateOrganization calls (removing the in-transaction Promise.all pattern).

Collects created/updated organization IDs during the transaction and triggers syncOrganization after the transaction commits, deduping IDs and isolating sync failures from DB writes.

^{Reviewed by Cursor Bugbot for commit 4e4dd48. Bugbot is set up for automated code reviews on this repo. 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.

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

[Copilot]

Pull request overview

This PR fixes intermittent savepoint "... " does not exist failures during member enrichment by removing parallel organization writes within a single pg-promise transaction (which can create conflicting nested savepoints) and deferring organization sync until after the transaction has committed.

Changes:

• Serialize findOrCreateOrganization calls (and related identity/merge-suggestion handling) by removing the prior Promise.all(...) pattern.
• Track organization IDs that need syncing during the transaction and run syncOrganization only after the outer transaction completes (deduped).

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.