fix: moving insightsProjects organization on merge

[ulemons]

Note

Low Risk
Small, targeted change that performs a straightforward DB update during merge; main risk is unintended bulk reassignment if organization IDs are wrong.

Overview
Fixes organization merge cleanup by also reassigning insightsProjects records from the secondary organization to the primary one.

Adds moveInsightsProjectsToAnotherOrganization in the data access layer (SQL UPDATE insightsProjects SET organizationId=... WHERE organizationId=... AND deletedAt IS NULL) and invokes it during finishOrganizationMergingUpdateActivities, alongside the existing activity-relation move.

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

[skwowet]

LGTM 🚀