feat: define repositories datasource [CM-884]

[mbani01]

This pull request adds a new data source definition for repositories in the services/libs/tinybird/datasources/repositories.datasource file. The new data source captures repository metadata and associations, supporting analytics and integration use cases.

Repository data source definition:

• Added a detailed description, schema, and configuration for the repositories data source, including fields for repository URLs, integration references, project associations, archival and exclusion status, timestamps, and parent repository tracking.
• Configured the data source to use the ReplacingMergeTree engine with partitioning by creation year and sorting by URL, optimizing for efficient querying and deduplication.

---

Note

Adds a new Tinybird repositories datasource for replicated repository metadata and associations.

• Defines schema fields for IDs, url, integration/project links, archival/exclusion flags, forkedFrom, and lifecycle timestamps (including deletedAt and lastArchivedCheckAt)
• Configures ReplacingMergeTree with partitioning by toYear(createdAt), sorting by url, and versioning via updatedAt; tagged as "Repositories"

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

Cursor Bugbot has reviewed your changes and found 1 potential issue.

[cursor]

Wrong sorting key causes incorrect deduplication behavior

High Severity

The ENGINE_SORTING_KEY is set to url instead of id, but the description states id is the primary key identifier. With ReplacingMergeTree, rows with the same sorting key are deduplicated, keeping the one with the highest updatedAt. Using url means repository renames (URL changes) will create duplicate records for the same repository that won't be deduplicated. Additionally, different repositories that somehow share a URL would be incorrectly merged. Other datasources in this codebase consistently use id as the sorting key.