feat: added the status field to all project related datasource and pipes

[emlimlf]

In this PR

• Added the project status field from the segments table to the insights_projects_populated_ds.datasource and updated the copy pipe that fills data to that
• Updated all the pipes and other data source that references the projects with the new status field

Ticket

IN-887

---

Note

Adds project status across Tinybird datasources and pipes for downstream consumers.

• Extend insights_projects_populated_ds schema with status; populate via insights_projects_populated_copy.pipe (LEFT JOIN segments)
• Update leaderboards_copy_ds schema and all leaderboards_* pipes to select/group/emit status
• Include status in insightsProjects_filtered, collections_list featured projects, and search_collections_projects_repos outputs

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

[cursor]

Missing FINAL on segments join inconsistent with file pattern

Medium Severity

The new LEFT JOIN segments lacks the FINAL keyword, inconsistent with all other ReplacingMergeTree table joins in this file (e.g., collectionsInsightsProjects FINAL, collections FINAL, integrations FINAL). The segments table uses ReplacingMergeTree with ENGINE_VER updatedAt. Without FINAL, unmerged updates could cause the join to return multiple rows per segment with different status values, producing duplicate project rows in the output.

 

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

Column order mismatch in members leaderboard UNION

High Severity

The status field is added after githubHandle in leaderboards_members.pipe, but all other leaderboard pipes add status before githubHandle is appended by leaderboards_copy.pipe. In a UNION ALL, column position determines alignment, not names. This causes githubHandle values from members to be written to the status column and vice versa when combined with other leaderboards. The status field needs to be placed before githubHandle to match the column order of other pipes.