fix: secondary tiebreaker sorting for orgs when they have the same contribution count (IN-991)

[epipav]

When multiple orgs had the same contributor_count (primary sort field), sorting was not deterministic, which could cause the same org to appear on different pages.

Added org.id as a secondary sort key to ensure stable ordering and consistent pagination.

---

Note

Low Risk
Low risk: changes only the ORDER BY clause to make pagination deterministic when contribution counts tie; results order may shift for tied orgs but no data shape or calculations change.

Overview
Ensures deterministic ordering for the organizations leaderboard by adding id as a secondary sort in organizations_leaderboard.pipe (ORDER BY contributionCount DESC, id DESC).

This prevents tied contributionCount rows from reordering between requests/pages, improving pagination consistency.

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