chore: refactor sync insights project to common layer and use it in nango worker as well (CM-786)

[themarolt]

Note

Moves repository-to-insights syncing and segment repo queries into common services and the data-access layer, updates backend to use them, and adds a nango worker activity to trigger sync after GitHub processing.

• Common Services:
  • Add CommonIntegrationService.syncGithubRepositoriesToInsights(...) to upsert segmentRepositories, prune stale mappings, and update insightsProject.repositories.
  • Enhance settings decryption; add Redis dependency.
• Data Access Layer (DAL):
  • Integrations: add findRepositoriesForSegment(...), findNangoRepositoriesToBeRemoved(...), plain repo unmap helpers, and include segmentId in fetchIntegrationById.
  • Segments: add getGithubMappedRepos(...), getGitlabMappedRepos(...), and cross-segment URL checks.
  • Utils: standardize updatedAt to now().
• Backend:
  • API GET /segments/{id}/repositories: switch to DAL findRepositoriesForSegment.
  • IntegrationService: replace bespoke repo sync with CommonIntegrationService.syncGithubRepositoriesToInsights(...); use DAL for mapped repo queries; remove legacy segment-repo sync logic.
  • Remove segment repo query methods from SegmentRepository now provided by DAL.
• Nango Worker:
  • Add syncGithubReposToInsights activity and call it post GitHub connection processing to persist repositories to insights.

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

This PR is being reviewed by Cursor Bugbot

Details

Your team is on the Bugbot Free tier. On this plan, Bugbot will review limited PRs each billing cycle for each member of your team.

To receive Bugbot reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.

[mbani01]

LGTM! Perhaps @ulemons can double-check since he got more context on segmentRepositories just in case

[ulemons]

LGTM ✅