fix: filter out bad timestamp issue activities to prevent overflows

[epipav]

We have 1970-dated issue activities that cause overflows when calculating closedInSeconds and `respondedInSeconds. We now filter these activities out in the issue analysis copy pipe

---

Note

Filters out pre-1971 issue activities in the Tinybird issue analysis pipe to avoid timestamp overflows.

• Tinybird pipe services/libs/tinybird/pipes/issue_analysis_copy_pipe.pipe:
  • Add toYear(timestamp) >= 1971 filters to issues_opened and issues_closed queries.
  • Keep joins and calculations for closedInSeconds and respondedInSeconds unchanged.
  • Normalize pipe TYPE to copy.

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

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

[joanagmaia]

LGTM ✅

Do you think this might also be an issue for pull requests analysis data? So basically in all widgets where we rely on the timestamps and where we need to make calculations like resolvedAt, mergedAt, shouldn't we always exclude these activities? 🤔
Everywhere else where we have totals we should still include them