fix: use repos_to_channel for PR & issues

[mbani01]

This pull request updates the way channels are filtered in two Tinybird pipes to use the repos_to_channels mapping instead of directly querying the repositories table. This change ensures that the filtering logic is consistent with the current mapping between repositories and channels.

Query logic improvements:

• Updated the fallback channel filtering in issues_average_resolve_velocity.pipe to select channels from the repos_to_channels table instead of the repositories table.
• Updated the fallback channel filtering in pull_requests_average_resolve_velocity.pipe to select channels from the repos_to_channels table instead of the repositories table.

---

Note

Low Risk
Low risk SQL-only changes to channel filtering; main impact is which repos are included by default when repos isn’t provided.

Overview
Aligns Tinybird pipes to consistently filter activity by repos_to_channels rather than directly reading repositories URLs, fixing default/fallback repo scoping for issue and PR resolve-velocity metrics.

Simplifies pull_requests_filtered.pipe to always constrain pra.channel via repos_to_channels (removing the prior conditional fallback), and updates repos_to_channels.pipe so the repos parameter is optional and defaults to all non-excluded, enabled (and non-deleted) repositories.

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

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