feat: uses left join in query organizations

[ulemons]

Note

Medium Risk
Changes SQL join semantics for OrganizationRepository.findAndCountAll, which can alter which organizations appear (and counts) when aggregates are requested, especially for orgs lacking aggregate rows.

Overview
Updates the organizations advanced query in organizationRepository.ts to always LEFT JOIN organizationSegmentsAgg (previously INNER JOIN when include.aggregates was enabled).

This means organization list/count queries with aggregates will now include organizations even when no matching aggregate row exists for the requested segment (leaving aggregate fields NULL/coalesced), instead of filtering them out.

^{Reviewed by Cursor Bugbot for commit 2199c18. 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.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[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 changes the organizations advanced query SQL to always use a LEFT JOIN to organizationSegmentsAgg, regardless of whether aggregate fields are requested, so organizations without matching aggregate rows are still returned.

Changes:

• Replace the conditional INNER JOIN/LEFT JOIN selection for organizationSegmentsAgg with a consistent LEFT JOIN.
• Preserve the segment join predicate while altering join semantics (no longer filtering organizations out via the join).

---

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

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

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 2199c18. Configure here.}