chore: delay member identity conflict errored results (CM-994)

[themarolt]

Note

Medium Risk
Changes error-handling control flow by introducing long, randomized delays for a specific DB constraint failure, which could impact processing latency and backlog behavior if the match is too broad or frequent.

Overview
Adds a special-case error handler in DataSinkService.triggerResultError to detect the uix_memberIdentities_platform_value_type_verified uniqueness conflict and delay the failed result instead of immediately retrying/marking error.

The delay is randomized (10–120 minutes), is logged with the scheduled until time, and persists via repo.delayResult before returning early.

^{Written by Cursor Bugbot for commit 34ed4ed. 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.

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